OK I see that text encoded in hex works for now.
But now I am stuck on precisely what to put for Contract Type in my ContractOffer JSON.
In the Step By Step Guide, the ContractType was a value that is not precisely one of the listed Contract Type values in the various docs such as in the tokenized.pdf white paper.
The Step By Step Guide in “Tokenized-smart-contract-agent-setup-final.pdf”
had this value:
“ContractType” : “Shareholder Agreement and Token Management”,
But “Shareholder Agreement and Token Management” is not the precise value of any documented Contract Type. So is the ContractType field not really checked when the ContractOffer is submitted?
Table 4.12.1 in the white paper had a mapping between ContractType and Asset Type.
But many of the Contract Type values in table 4.12.1 are blank. Why are they blank?
If I search all the source code of smart-contract-master, “Currency” is not found.
But “Currency” is listed in https://tokenized.com/docs/protocol/assets#currency as one of the “Available Assets”.
So why is “Currency” not found in the source code?
I had been particularly interested to try Contract Type / Asset Type “Simple Agreement for Future Equity (SAFE)” as listed in the White paper but now I see that it is not implemented in the current source code. So I wanted to try using the closest Asset type most similar to SAFE, and that looks like “Coupon” but the white paper lists Coupon as only a Utility Token and the ContractType is blank.
Is Coupon a Smart Contract or something less functional? I would like to use it for my evaluation experiments in place of SAFE until SAFE is implemented. Is there any downside to using a Coupon?
Coupon has a Value field whereas most of the of other Assets do not have that. I think I can use the Value field to partly mimic the equity value in a SAFE for now.
What is the ETA for SAFE being supported in the code?