I have had alot of controversies over the last one but I have decided to share this one;
P/s: I'm a tutor and I add everything I learn to my tutoring scheme
ofcourse,that's how it works. For this reason, I will really be pleased if every reply is properly ascertain💆
Section 1:
Assets are pseudonymously represented by iDs
i came to realize that even though this asset have IDs, the anonymity is maintained. These definitely means that asset don't have any prior means of recognition or identification without their IDs which, ofcourse has to be hashed by the issuer, using an already generated privkey right? I need more clarity.
Q1
Section 2:
The maker output starts with an OP_RETURN opcode but it must contain PUSHDATA opcodes
containing a parsable Open Assets marker payload. If multiple parsable PUSHDATA opcodes exist in the same output, the first one is used, and the other ones are ignored.Q3:
• i haven't really run SHA256 hashes on mainet so I don't know if PUSHDATA produces the same random figures on different trnx? That's not true right?
•Are those PUSHDATA some compacted replicable codes so for that reason, anyone of them could function?
• if at the tail end,one phase of the code serves, what's the point of replication then?
security?Lastly, someone made a post bout OP_RETURN weeks ago(should be @NotAtheter, @ETFbitcoin or @blackHatCoiner?) if only I can vividly remember.... The OP was curious bout main function of OP_RETURN; the above should serve as one major function☺️
Sorry if the whole thing is cumbersome....feel free to drop your ideas cus I LEARN AS I TEACH.
The ILLUS at GitHub
https://github.com/OpenAssets/open-assets-protocol/blob/master/specification.mediawikiSandra