diff --git a/templates/MetaLeX cyberSAFT Reg S raise v 1.0.md b/templates/MetaLeX cyberSAFT Reg S raise v 1.2.md similarity index 82% rename from templates/MetaLeX cyberSAFT Reg S raise v 1.0.md rename to templates/MetaLeX cyberSAFT Reg S raise v 1.2.md index 62c2f515..f8645df5 100644 --- a/templates/MetaLeX cyberSAFT Reg S raise v 1.0.md +++ b/templates/MetaLeX cyberSAFT Reg S raise v 1.2.md @@ -2,9 +2,13 @@ id: bytes32(uint256(35)) -combined doc: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeidquzma24o53tiys7kvspvx5izc7iru5n5dfgfwmxefi3qd67ou2y +legalURI: +saftURI: ipfs://bafybeighy3fgweoeivmxnp62ryrckn7xgtjerrsefrkxrruea6tq2q6gyi -SAFT alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeieqiarv2kqdbkmvrf2o6powu375hayji54gauqhqpz2kfmypao6nm + +combined doc: [https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeidquzma24o53tiys7kvspvx5izc7iru5n5dfgfwmxefi3qd67ou2y](https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeibwrz3rttteguo5ccoh5x7ndwdu6hyhy7i3iraii5c5ml4pfv73t4) + +SAFT alone: [https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeieqiarv2kqdbkmvrf2o6powu375hayji54gauqhqpz2kfmypao6nm](https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeighy3fgweoeivmxnp62ryrckn7xgtjerrsefrkxrruea6tq2q6gyi) ## Global Fields @@ -21,6 +25,7 @@ SAFT alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeieqiarv2 | unlockingCliffPeriod | Duration in `unlockingIntervalType`, first tokens unlocked at `unlockingStartTime` + `unlockingCliffPeriod` | | unlockingCliffPercentage | e.g. "10.5%" | | unlockingIntervalType | "secondly", "hourly", "daily", "monthly", "blockly". Note that this affects both `unlockingPeriod` and `unlockingCliffPeriod` | +| customProvisions | an arbitrary string intended to insert any custom provision the parties agree upon | ## Party Fields @@ -37,7 +42,7 @@ SAFT alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeieqiarv2 ## Certificate Extension -name: TokenWarrantExtension +name: SAFTExtension ```solidity struct SAFTData { UnlockStartTimeType unlockStartTimeType; // enum of different types, can be agreementStartTime, tgeTime, or setTime @@ -46,6 +51,7 @@ struct SAFTData { uint256 unlockingCliffPeriod; uint256 unlockingCliffPercentage; UnlockingIntervalType unlockingIntervalType; - // blockly, secondly, daily, weekly, monthly + string customProvisions; // an arbitrary string intended to insert any custom provision the parties agree upon } ``` @@ -79,4 +85,4 @@ UNREGISTERED SECURITIES LEGEND. THIS INSTRUMENT, THE CERTIFICATE TOKEN AND ANY S [4] contentious hardfork legend. -CONTENTIOUS HARDFORK LEGEND. IN THE EVENT THAT THE BLOCKCHAIN SYSTEM ON WHICH THE CERTIFICATE TOKEN WAS ORIGINALLY ISSUED UNDERGOES A PERSISTENT “CONTENTIOUS HARDFORK” (AS COMMONLY UNDERSTOOD IN THE BLOCKCHAIN INDUSTRY, RESULTING IN TWO INDEPENDENT BLOCKCHAIN SYSTEMS THAT ARE BOTH REASONABLY EXPECTED TO HAVE INDEPENDENT PERSISTENT COMMERCIAL VALUE), NO COPY OF THE CERTIFICATE TOKEN MAY BE OFFERED, SOLD, OR OTHERWISE TRANSFERRED, PLEDGED, OR HYPOTHECATED UNTIL THE COMPANY HAS DETERMINED, IN ITS SOLE AND ABSOLUTE DISCRETION, WHICH BLOCKCHAIN SYSTEM (AND WHICH CERTIFICATE TOKENS) TO TREAT AS CANONICAL, AND THEN ONLY THE CERTIFICATE TOKEN THUS DETERMINED BY THE COMPANY TO BE CANONICAL MAY BE OFFERED, SOLD, OR OTHERWISE TRANSFERRED, PLEDGED, OR HYPOTHECATED (TO THE EXTENT OTHERWISE PERMITTED). IN THE EVENT THAT THE BLOCKCHAIN SYSTEM DETERMINED BY THE COMPANY TO BE CANONICAL FOLLOWING A CONTENTIOUS HARDFORK ITSELF SUBSEQUENTLY UNDERGOES ANOTHER CONTENTIOUS HARDFORK, THIS RESTRICTIVE LEGEND SHALL LIKEWISE APPLY TO SUCH OTHER CONTENTIOUS HARDFORK, MUTATIS MUTANDIS. \ No newline at end of file +CONTENTIOUS HARDFORK LEGEND. IN THE EVENT THAT THE BLOCKCHAIN SYSTEM ON WHICH THE CERTIFICATE TOKEN WAS ORIGINALLY ISSUED UNDERGOES A PERSISTENT “CONTENTIOUS HARDFORK” (AS COMMONLY UNDERSTOOD IN THE BLOCKCHAIN INDUSTRY, RESULTING IN TWO INDEPENDENT BLOCKCHAIN SYSTEMS THAT ARE BOTH REASONABLY EXPECTED TO HAVE INDEPENDENT PERSISTENT COMMERCIAL VALUE), NO COPY OF THE CERTIFICATE TOKEN MAY BE OFFERED, SOLD, OR OTHERWISE TRANSFERRED, PLEDGED, OR HYPOTHECATED UNTIL THE COMPANY HAS DETERMINED, IN ITS SOLE AND ABSOLUTE DISCRETION, WHICH BLOCKCHAIN SYSTEM (AND WHICH CERTIFICATE TOKENS) TO TREAT AS CANONICAL, AND THEN ONLY THE CERTIFICATE TOKEN THUS DETERMINED BY THE COMPANY TO BE CANONICAL MAY BE OFFERED, SOLD, OR OTHERWISE TRANSFERRED, PLEDGED, OR HYPOTHECATED (TO THE EXTENT OTHERWISE PERMITTED). IN THE EVENT THAT THE BLOCKCHAIN SYSTEM DETERMINED BY THE COMPANY TO BE CANONICAL FOLLOWING A CONTENTIOUS HARDFORK ITSELF SUBSEQUENTLY UNDERGOES ANOTHER CONTENTIOUS HARDFORK, THIS RESTRICTIVE LEGEND SHALL LIKEWISE APPLY TO SUCH OTHER CONTENTIOUS HARDFORK, MUTATIS MUTANDIS.