PRISM Protocol S.P., a segregated portfolio of Futarchy Governance SPC
What the chain and the MetaLeX indexer record about this cyberCORP. No wallet or account is needed to read it, and every address links to the block explorer so you can check it yourself.
Entity
- Entity type
- Segregated Portfolio of Segregated Portfolio Company
- Jurisdiction
- Cayman Islands
- Formation source
- MetaDAOFormed through the MetaDAO launchpad factory.All MetaDAO companies
- Deployed onchain
- Jun 01, 2026 (UTC)The date the company's contracts were deployed. The legal formation date may differ.
- Chain
- Base (chain ID 8453)
- Formation factory
- 0x734ae2b36f663d0f4233ce4a02c13b5eb8ec959d
Entity type and jurisdiction are what the company recorded onchain at formation. This page does not check them against a government registry.
Contracts and deployed versions
- CyberCorp0x2dd062f438e791504313c3ae99b2e093d43ed9f9Could not be readReference could not be read
- Issuance Manager0xc3304b1cbb48bf2f683ab05d273d0ca2ecee34e1Could not be readReference could not be read
- Deal Manager0x68c49ff4250afa2189b097680ee2f773a0922ee8Could not be readReference could not be read
- Round ManagerNot deployed
- BorgAuth0x87f03a53675d8149ca40edf3c0e307273e4980d9Version not read by this page
Versions are read live from each contract when this page loads. The comparison is against the reference implementation published by the factory each contract is bound to.
A live read failed. Nothing is shown in its place.
Officers
The officer roster the company keeps in its CyberCorp contract, as indexed. Titles are free text the company recorded.
- Akash Chakraborty ยท Operator0x5b50afe39f908c90e41806a7529d7374a4246515Recorded Jun 01, 2026
Security classes onchain
Each class is a certificate contract (CyberCertPrinter) the company deployed. Counts are certificates minted onchain, including any later voided.
This company has not created a security class onchain.
Registered agreements
Agreements registered in the same transaction that deployed the company. Launchpad factories register formation documents this way. The indexer does not attribute later agreements to a company, so they are not listed.
- MetaDAO Futarchy Governance SPC - Board Consent - Approval of SegCo v 1.0SignedRegistered Jun 01, 2026Agreement ID 0x0804e0402a091807521ea45aa23aefcf511167ee6be69979cf850ba25b2ce7beTransaction 0x67668a4ae8a8a9d8a0fb28e5294510d072e7048c6e97fcf5d584dc975f303caaOpen the document on IPFS
- MetaDAO Futarchy Governance SPC - SegCo combined v 1.0SignedRegistered Jun 01, 2026Agreement ID 0x556e2ad65ec1b6dc5731731a9218cdf868cdb0ad222082b0186f8d390a76a004Transaction 0x67668a4ae8a8a9d8a0fb28e5294510d072e7048c6e97fcf5d584dc975f303caaOpen the document on IPFS
Public rounds
Rounds the company advertises publicly. Private rounds are not listed.
This company has no public round.
Chronology
Assembled from indexed onchain events, oldest first. Dates are block times in UTC.
- Jun 01, 2026Company deployed onchainFormed through the MetaDAO launchpad factory.
- Jun 01, 2026Officer recorded: Akash ChakrabortyOperator
- Jun 01, 2026Agreement registeredMetaDAO Futarchy Governance SPC - Board Consent - Approval of SegCo v 1.0
- Jun 01, 2026Agreement registeredMetaDAO Futarchy Governance SPC - SegCo combined v 1.0
- Contract upgrades are not indexed. The versions above are the ones deployed now.
- Officer removals and title changes are not kept as history. Only current officers appear, dated from their current record.
- The indexer does not record when a security class was created.
What this page does not show
- Filing status with any state or national registry. It makes no statement about good standing.
- The cap table. There are no holders, positions or ownership percentages here. Which record is the company's securities ledger depends on its governing documents, and this page makes no claim about it.
- Document contents, and agreements registered after the company was deployed.
- Private rounds, deals, investors, and contact details for anyone.
- Anything held offchain by the company or by MetaLeX. Every fact above comes from the chain or from the public MetaLeX indexer.
