DecentralChainDecentralChain
  • Technologysubmenu
    Why DecentralChainWhat sets this chain apartHow the chain worksPublic blocks, public validatorsBlockchain featuresWhat is on, what is being voted onFinalityThe rollback bound, and what is unverifiedRIDEContracts that cannot run foreverFor machinesUnsigned transactions and RIDE in processSolana bridgePhantom and Solflare, mainnet onlyNetwork statusHeight, sync and peers, read live
  • Ecosystemsubmenu
    DCC public saleOpens 26 SeptemberDecentralCoinSupply, allocation and tokenomicsDecentral.ExchangeexternalDecentralPropDecentralScansoonCubensis ConnectDecentralAmericasoon
  • Developerssubmenu
    QuickstartRead, compile and composeREST APIEvery endpoint, no key, no accountSDK packages19 on npm, 5 in the workspaceSigningAuthorising without custodyMCP & AgentsThe chain, and the tools we have builtDecentralChain NodeRun a validator, and what LPoS pays
  • Communitysubmenu
    ChannelsTelegram, X and the reposDCC AirdropAllocated, not yet arrangedGovernanceWho can actually decide anythingBrand kitThe mark, and how to use it
  • Documentation
XGitHub
Start buildingarrow
DecentralChainDecentralChain

An open Layer-1 with Leased Proof of Stake.

Native token: DecentralCoin (DCC)

Fixed supply 100,000,000 DCC
Minted at genesis, never inflated

  • X
  • GitHub
  • Telegram

Build

  • Quickstart
  • REST API
  • SDK packages
  • Signing
  • MCP & Agents
  • Documentation

Ecosystem

  • DCC public sale
  • DecentralCoin
  • Decentral.Exchange
  • DecentralProp
  • DecentralSwap
  • Cubensis Connect

Network

  • Blockchain features
  • Finality
  • RIDE
  • Solana bridge
  • Run a node
  • Network status

Project

  • Community
  • DCC Airdrop
  • Governance
  • Brand kit
  • GitHub
mainnetHeight—Node—read from your browser
© 2026 DecentralChainOperated by DecentralExchange · Cédula Jurídica 3-102-956858
Jacó, Garabito, Costa Rica
TermsPrivacySecurityLicensingdecentralchain.io

Cubensis Connect

The wallet that keeps
your keys in the extension

Cubensis Connect is the browser extension for DecentralChain. It holds your seed encrypted inside the extension, signs transactions a site asks for, and gives that site no way to read the key it signed with. Nothing on this page is a plan: it describes what the extension does today, and its current limits alongside it.
BrowsersChrome MV3, Firefox MV2HardwareLedgerLicenceProprietary, source available

On this page

  • What it is
  • Installing it
  • How your keys are held
  • The CubensisConnect API
  • Current limits
  • Source and licence

What it is

A browser extension that lets a web page ask for a signature without ever handling your seed. The page calls a method, the extension shows you what is being signed, and you approve or reject it. The signature goes back to the page. The key does not.

  • Multiple wallets in one extension, switched without re-entering a seed.
  • One-click signing once an account is unlocked, so a transaction does not mean retyping anything sensitive.
  • Password recovery from the seed phrase. Forgetting the password does not lose the account, because the seed is what the account actually is.
  • Ledger hardware support, for keys that never exist in software at all.
  • Mainnet, testnet and stagenet.

Installing it

Careful
There is no Chrome Web Store or Firefox Add-ons listing yet. Until one is published, the only honest way to install Cubensis Connect is to build it from source and load it unpacked. Any listing claiming to be Cubensis Connect before then is not ours.

The repository carries the build and the instructions. It targets Node 24 or newer, and produces a Chrome MV3 build and a Firefox MV2 build from the same source.

How your keys are held

Seed phrases and private keys are encrypted and stored inside the extension. A dApp cannot read them, and completing a transaction never requires entering sensitive information into the page requesting it. That separation is the entire reason the extension exists rather than a web wallet.

It is worth being plain about what this does and does not protect. It stops a malicious site from reading your key. It does not stop you approving a transaction that does something you did not intend, so read what the extension shows you before approving it.

The CubensisConnect API

On any page served over http or https with the extension installed, a CubensisConnect global appears. Local file:// pages do not get it. The README documents 18 methods on it:

publicState notification encryptMessage decryptMessage on auth signTransaction signAndPublishTransaction signTransactionPackage signOrder signAndPublishOrder signCancelOrder signAndPublishCancelOrder signRequest signCustomData resourceIsApproved resourceIsBlocked verifyCustomData

Two published packages exist for talking to it from TypeScript: @decentralchain/cubensis-connect-provider and @decentralchain/cubensis-connect-types, both at 1.0.0 on npm.

Current limits

Careful
Bridge withdrawals do not work from a Cubensis account. Withdrawing across the Solana bridge means calling burnToken on DecentralChain, and that path currently works for seed accounts only. Ledger and Cubensis users cannot call it. Bridge deposits are unaffected, because those are Solana-side transactions.

Source and licence

The source is public, and the licence is not an open-source one. Cubensis Connect is copyright Blockchain Costa Rica, all rights reserved, originally derived from Keeper Wallet (copyright DLTech Ltd, 2022). You are granted a non-exclusive, non-transferable licence to use it and to contribute to the repository. Copying, modifying, publishing, selling, redistributing or reverse engineering it are not permitted.

Read LICENSE.md in the repository before building on it. Source available is not the same thing as open source, and the difference matters if you intend to ship something derived from it.

Next

Read the source

The repository, the build, the API reference and the licence in full.