Skip to content

Update and rename MetaLeX cyberSAFE jx-neutral-style Reg S raise v 1.… #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lex-node wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Update and rename MetaLeX cyberSAFE jx-neutral-style Reg S raise v 1.… #71

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
acc01c8
Update and rename MetaLeX cyberSAFE jx-neutral-style Reg S raise v 1.…
lex-node Jan 18, 2026
c660857
Close SAFEData code fence
lex-node Jan 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions ...AFE jx-neutral-style Reg S raise v 1.0.md → ...AFE jx-neutral-style Reg S raise v 1.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,11 @@
id: bytes32(uint256(32))

legalURI:
safeURI: IPFS://bafybeib5pqnqwbfdsnv4lqdkdglz2e4xqz2qklwdzzpbftydopzuqnri2a
safeURI: ipfs://bafybeigkcbocfq3p7rscojjej24jajyrhqk6mukgetmlsmyo4f6cp6iqry

combined doc: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeib5pqnqwbfdsnv4lqdkdglz2e4xqz2qklwdzzpbftydopzuqnri2a
combined doc: [https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeib5pqnqwbfdsnv4lqdkdglz2e4xqz2qklwdzzpbftydopzuqnri2a](https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeieh7jn553jmrjmwee3dsvwf5hkedomey2vhubc3mumlewfpumvlae)

SAFE alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeifvtc4xupzf3mf6pgtzxsyby2uhxbzuh77cggy4bmgpddaupx5j4i
SAFE alone: [https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeifvtc4xupzf3mf6pgtzxsyby2uhxbzuh77cggy4bmgpddaupx5j4i](https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeigkcbocfq3p7rscojjej24jajyrhqk6mukgetmlsmyo4f6cp6iqry)

## Global Fields

Expand All @@ -18,6 +18,7 @@ SAFE alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeifvtc4xu
| expirationTime | |
| governingJurisdiction | |
| disputeResolution | |
| customProvisions | an arbitrary string intended to insert any custom provision the parties agree upon |

## Party Fields

Expand All @@ -32,7 +33,12 @@ SAFE alone: https://beige-just-flyingfish-108.mypinata.cloud/ipfs/bafybeifvtc4xu

## 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)

Expand Down Expand Up @@ -62,4 +68,4 @@ REGULATION S LEGEND. THIS SAFE AND THE CERTIFICATE TOKEN HAVE NOT BEEN, AND WILL

[3] 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.
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.
Loading