Legacy V3 / nPEG Contract Model
V3 is the old token-gated ERC-721 model. It is no longer the soToken direction. Keep this page as historical context for the future nPEG route.
The V3 contracts were useful, but they drifted away from the intended soToken design. V3 produced standard ERC-721 objects gated by ERC-20 holdings. That makes them easier to trade on outside NFT marketplaces, but it does not create a uPEG-style balance-bound object.
What V3 was
V3 used:
- token-gated public minting
- standard ERC-721 ownership
- ERC-2981 royalties
HeldTokenandIntegrationBornbirth labels- raw gate balance recorded at mint
- a standard NFT marketplace listing flow
- Lower Fee Tier marketplace settings
Those mechanics are now treated as legacy/nPEG material.
What soToken is now
soTokens use a source-token balance as the object support layer.
The live V4 direction is:
- native LOA/BOA launches first
- future external-token compatibility for already-existing ERC-20 communities
- balance records instead of standalone ERC-721 birth records
claimandclaimForinstead of ERC-721 minting- specific object transfer
- creator-selected seed modules
- creator-approved birth hooks
- one-way legacy receipt conversion only when a creator enables it
Why V3 became nPEG
V3 is still valuable for the future nPEG path because it is ERC-721 compatible. It can serve projects that explicitly want classical NFT behavior, outside marketplace compatibility, and ERC-2981 receipts.
It should not be marketed as the core soToken product.
Archived source boundary
The old source files are preserved for nPEG foundation work, not removed:
contracts/src/BpegFactory.solcontracts/src/BpegCollection.solcontracts/src/BpegRouter.solcontracts/src/BpegMarketplace.solcontracts/src/BpegHook.solcontracts/src/BpegRendererV2.solcontracts/src/BpegTraitStorageV2.sol
The explicit archive marker is contracts/src/npeg/README.md. Frozen snapshots also remain in contracts/archive.
Copy rule
Public docs and app copy should not call V3 ERC-721 collections "soTokens." Use:
- soToken for the current v1.2 object-token family
- LOA and BOA for the current launchable object classes
- nPEG for the old ERC-721-style NFT route when it returns
- vBundle only for the separate future bundle product