Re: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"
...
The CLAMour system did influence my thinking about registering identities. Are you suggesting I should use CLAMour directly for this purpose? Since the "getclamour" command is being added, this would be easiest for me. I was thinking I'd need to keep track of the registry in a separate database.
Someone could register an identity using clamour by publishing a tx with CLAMspeech:
create clamour
where points to text like "I have public key 02... (clam address x...). I offer escrow services under XYZ terms." which hashes to . Then the first 8 hex characters of could be used to refer to this identity in future CLAMspeech records. In order to interpret the identity, the "getclamour" command could be used.
To be clear, if the clam devs object to me using CLAMour this way I won't. Maybe the clam devs could be a more general registry not just for petitions. Something like
create identity
and then "getidentity" that works the same way as CLAMour, but with a different "space."
...
I'm not sure exactly what your goal is, but it sounds like Namecoin could be a viable alternative.The CLAMour system did influence my thinking about registering identities. Are you suggesting I should use CLAMour directly for this purpose? Since the "getclamour" command is being added, this would be easiest for me. I was thinking I'd need to keep track of the registry in a separate database.
Someone could register an identity using clamour by publishing a tx with CLAMspeech:
create clamour
where points to text like "I have public key 02... (clam address x...). I offer escrow services under XYZ terms." which hashes to . Then the first 8 hex characters of could be used to refer to this identity in future CLAMspeech records. In order to interpret the identity, the "getclamour" command could be used.
To be clear, if the clam devs object to me using CLAMour this way I won't. Maybe the clam devs could be a more general registry not just for petitions. Something like
create identity
and then "getidentity" that works the same way as CLAMour, but with a different "space."
...
CLAMour is one application of the overall ClamSpeech system, created for petitions. So if you want to store identities, I would recommend something along the lines of 'create identity ' as per your example. At one point we explored a potential format for ClamSpeeches that included metadata before the rest of the ClamSpeech - a "category identifier." Ultimately something more plain-language was used.
There are no enforced rules on the contents of ClamSpeeches (and I'm confident that there never will be), only on their lengths. So if somebody wants to store identity data in the CLAM chain, it doesn't really matter what anyone else approves of.
If you do use the CLAM chain for identity data, there is one thing you should be aware of: The requirement that a petition be declared with 'create clamour []' exists because petitions are identified by their first 4 bytes when voting for them (so multiple petitions can be voted for in one stake transaction). Since you probably won't need to refer to multiple identities in one ClamSpeech, you can just omit the 'create identity' step. Thus, you can simply put 'identity []' in a ClamSpeech instead of 'create identity []'.