From a0d69aa3c5b6455f9daea46222862eff2d0b9dac Mon Sep 17 00:00:00 2001 From: _g4brielShapir0 Date: Sun, 18 Jan 2026 16:50:04 -0500 Subject: [PATCH 1/2] Update and rename MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.0.md to MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md --- ...cyberSAFE jx-neutral-style Reg D raise v 1.1.md} | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) rename templates/{MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.0.md => MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md} (78%) diff --git a/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.0.md b/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md similarity index 78% rename from templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.0.md rename to templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md index b87a2776..48e78372 100644 --- a/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.0.md +++ b/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md @@ -3,11 +3,11 @@ id: bytes32(uint256(30)) legalURI: -safeURI: IPFS://bafybeiazn4jdtlu4yz7lqbfhzaxsfhsfuwaq55m4x5mhjdeddbwwrhfufe +safeURI: IPFS://bafybeidq7z4sgbh5tqxfehs5rz3r3il76ony3t7psetwge5ctld6lubi5e -combined doc: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeiazn4jdtlu4yz7lqbfhzaxsfhsfuwaq55m4x5mhjdeddbwwrhfufe +combined doc: [https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeiazn4jdtlu4yz7lqbfhzaxsfhsfuwaq55m4x5mhjdeddbwwrhfufe](https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeih7l2kxncjuwrfgv5gnmpcik43dnn4pxpe4it4u7ti2hgfgrlot2a) -SAFE alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeiafzkynirjta4pd3g365qv6ttlz3pkeqcquhbald7nqqfmm5vpfua +SAFE alone: [https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeiafzkynirjta4pd3g365qv6ttlz3pkeqcquhbald7nqqfmm5vpfua](https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeidq7z4sgbh5tqxfehs5rz3r3il76ony3t7psetwge5ctld6lubi5e) ## Global Fields @@ -18,6 +18,7 @@ SAFE alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeiafzkyni | expirationTime | | | governingJurisdiction | | | disputeResolution | | +| customProvisions | an arbitrary string intended to insert any custom provision the parties agree upon | ## Party Fields @@ -32,7 +33,11 @@ SAFE alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeiafzkyni ## Certificate Extension -none. +name: SAFEExtension +```solidity +struct SAFEData { + string customProvisions; // an arbitrary string intended to insert any custom provision the parties agree upon +} ## CertificateDetails Struct (for reference) From d1ed9be358682d6599cfb0d07bcc7cf31f698feb Mon Sep 17 00:00:00 2001 From: _g4brielShapir0 Date: Sun, 18 Jan 2026 17:12:49 -0500 Subject: [PATCH 2/2] Fix SAFEData code fence --- .../MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md b/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md index 48e78372..f4f7e5df 100644 --- a/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md +++ b/templates/MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.1.md @@ -38,6 +38,7 @@ name: SAFEExtension struct SAFEData { string customProvisions; // an arbitrary string intended to insert any custom provision the parties agree upon } +``` ## CertificateDetails Struct (for reference) @@ -70,4 +71,3 @@ THIS SAFE, THE CERTIFICATE TOKEN AND ANY SECURITIES ISSUABLE PURSUANT HERETO OR [4] 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. -