Implemented in the project
- NFT gallery, whitelist/public minting, and admin surfaces
- Wallet connection on Base Sepolia testnet
- Cloudflare Pages / Workers with IPFS and R2 storage paths
CinaChain / Base Sepolia beta.
CinaChain’s repository includes an NFT DApp, portal, documentation, smart contracts, and Cloudflare edge services. The current release scope is Base Sepolia testnet; documented domains are not proof of a live production deployment.
Product evidence / current scope.
Status and capabilities below are tied to public project repositories. They do not imply a customer deployment, managed SLA, or production availability beyond the linked evidence.
The repository is configured for testnet assets. Its documented domain topology is not proof of a live production deployment.
Verified: · commit 7b5cde5
Example data generated by this site—not a customer screenshot or proof of a live deployment.
Capabilities.
These are reference workflow patterns, not a promise that every capability is enabled in every release or deployment. Start with the smallest useful workflow and confirm current availability against the evidence above.
Display collection assets with documented multi-gateway IPFS image fallback.
Use Reown AppKit with wagmi and viem against one explicit test network.
Run the repository’s Merkle-tree whitelist and public-phase paths with testnet assets.
Use the included admin surfaces for whitelist management and contract operations.
Keep portal, DApp, docs, billing, and whitelist units explicit in the Cloudflare release topology.
Run quality gates and verify custom domains and live revisions after each release.
Workflow.
A reference evaluation keeps the selected network, wallet, phase, contract state, and explorer result visible.
Illustrative testnet contract.
Use explicit inputs, review points, and outputs so the system is easier to operate and change.
mint "testnet-collection" {
network = "base-sepolia"
phase = "whitelist-or-public"
assetType = "testnet-only"
}Operating principles.
Beta and Base Sepolia scope should stay visible wherever the product is described.
Network, mint phase, contract, and explorer links should remain inspectable.
Repository configuration must be paired with post-deploy domain and revision checks.
Next step.
Tell us the work, systems, constraints, and review points your team already has. We will help identify a sensible starting scope.