Skip to content

Comments

Add SAFTE template in templates folder#77

Open
lex-node wants to merge 3 commits intodevelopfrom
codex/add-safte-template-to-extensions-folder
Open

Add SAFTE template in templates folder#77
lex-node wants to merge 3 commits intodevelopfrom
codex/add-safte-template-to-extensions-folder

Conversation

@lex-node
Copy link
Contributor

Motivation

  • Provide a SAFTE template matching the existing SAFT/TokenWarrant templates so the SAFTEExtension in src/storage/extensions/SAFTEExtension.sol has a corresponding human-readable template and UI field mapping, with unknown URLs left as placeholders.

Description

  • Add documentation file templates/MetaLeX cyberSAFTE reg D v 1.0.md that defines global fields, party fields, the SAFTEData extension struct (aligned with SAFTEExtension), relevant enums, and restrictive legends, with bracketed placeholders for external URIs and IDs.

Testing

  • No automated tests were run because this is a documentation-only change and does not affect compiled contracts.

Codex Task

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d9f707323a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

| expirationTime | time at which offer to sign agreement (purchasing the SAFTE) expires |
| governingJurisdiction | jurisdiction of incorporation and also jurisdiction of governing law for the agreement |
| disputeResolution | method of dispute resolution |
| unlockStartTimeType |"tokenWarrantTime" \|"tgeTime" \| "setTime" |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align unlockStartTimeType value with SAFTEExtension

The template lists unlockStartTimeType values as tokenWarrantTime|tgeTime|setTime, but SAFTEExtension serializes tokenWarrantTime to the string agreementDateTime (see src/storage/extensions/SAFTEExtension.sol around lines 137–140). If clients or the UI validate SAFTE metadata against this template, they will reject or mis-map the on-chain value, breaking SAFTE metadata rendering. Consider updating the template to use agreementDateTime (or adjusting the extension) so the documented values match what the contract emits.

Useful? React with 👍 / 👎.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@merisman will leave it to you to evaluate and resolve this comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant