Sluice Network 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
- Jul 05, 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
- CyberCorp0x94b2a77a043b4fec64bd615ac44f7f2e69f187a9Could not be readReference could not be read
- Issuance Manager0x8bb78e39547c468e13f92621abb2683e6b462117Could not be readReference could not be read
- Deal Manager0x780f1bff2214e18b4314ec459576d062e974739dCould not be readReference could not be read
- Round ManagerNot deployed
- BorgAuth0xa13ce05a8deb0d7c48246d1d95a3bde14c569fb6Version 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.
- Unnamed officer ยท Operator0x2161f1b4c5deb41693392905ffc8afb66c70ac25Recorded Jul 05, 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 - SegCo combined v 1.0SignedRegistered Jul 05, 2026Agreement ID 0x339b5818870225f88259a3a0201435435a008cba6832df20ea2be5f992634e22Transaction 0x3c5df7e7f2f1f88cc8486b1791185a2a9846dba36834c0a55c3254f2e513663dOpen the document on IPFS
- MetaDAO Futarchy Governance SPC - Board Consent - Approval of SegCo v 1.0SignedRegistered Jul 05, 2026Agreement ID 0xc95f7c858dbd18ac41dc0a84cba996e569d8decaebebd886a2d0851f04c15f30Transaction 0x3c5df7e7f2f1f88cc8486b1791185a2a9846dba36834c0a55c3254f2e513663dOpen 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.
- Jul 05, 2026Company deployed onchainFormed through the MetaDAO launchpad factory.
- Jul 05, 2026Officer recorded: Unnamed officerOperator
- Jul 05, 2026Agreement registeredMetaDAO Futarchy Governance SPC - SegCo combined v 1.0
- Jul 05, 2026Agreement registeredMetaDAO Futarchy Governance SPC - Board Consent - Approval of SegCo 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.
