Skip to content

Update and rename MetaLeX cyberSAFT Reg S raise v 1.0.md to MetaLeX c… #70

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 cyberSAFT Reg S raise v 1.0.md to MetaLeX c… #70

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e892f03
Update and rename MetaLeX cyberSAFT Reg S raise v 1.0.md to MetaLeX c…
lex-node Jan 18, 2026
6efda66
Fix saftURI IPFS scheme
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
14 changes: 10 additions & 4 deletions ...es/MetaLeX cyberSAFT Reg S raise v 1.0.md → ...es/MetaLeX cyberSAFT Reg S raise v 1.2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
}
```

Expand Down Expand Up @@ -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.
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