Platform implementation

Polygon (PoS and CDK)

We deploy on Polygon PoS or launch a dedicated chain with Polygon CDK, choosing between them on control, cost and who should run the infrastructure.

Fibre splice tray with neatly coiled optical fibres

The first decision is architectural: share Polygon PoS with everyone else, or run your own chain built with the CDK and connected to the AggLayer. Gulf issuers of tokenised assets weigh that choice against regulation. ADGM's FSRA and the DFSA in DIFC each run a virtual asset regime, and the CMA oversees securities in Saudi Arabia, so legal and compliance help scope a dedicated chain from the start.

On Polygon PoS we deploy contracts, run Bor and Heimdall nodes where the product needs its own RPC, and plan for POL as the gas token. For a CDK chain we configure the sequencer, prover and bridge, choose rollup or validium data availability, and set up a block explorer and indexers before any user arrives.

Polygon (PoS and CDK) and related product names may be trademarks of their respective owners.

How we implement Polygon (PoS and CDK)

Design, build, integration and run-state support, with each decision recorded for your steering committee.

  • Blueprint and governance

    Shared chain or dedicated chain, data availability mode, sequencer operator and bridge limits: the CTO, product and risk decide these before deployment.

  • Sequencer and prover operations

    Run books, monitoring and failover for a CDK chain's sequencer and prover, with a named owner on call.

  • Bridge controls

    Bridge limits, pause roles and multi-signature approvals for moving assets between Ethereum and your chain.

  • Gas and fee policy

    A decision on the chain's gas token and fee level, or sponsored transactions on PoS, so customers see predictable costs.

  • Hypercare and managed support

    Polygon upgrades its protocol through announced hard forks, so we schedule node updates ahead of each one and monitor checkpoints to Ethereum, bridge activity and sequencer uptime.

Choosing Polygon for your chain

Teams wanting EVM compatibility at lower fees than Ethereum mainnet are the usual fit, as are issuers who may later need their own chain without leaving familiar Ethereum tooling.

  • Contracts already written for the EVM
  • A clear view on whether you need your own chain or a shared one
  • An operations team able to run a sequencer, or a provider who will
  • Legal advice on the assets that will cross the bridge

Plan Polygon (PoS and CDK) with Hosn Al Tomoh

Tell us what the platform needs to do and when. We will propose a first phase with scope, team and an itemised quotation.

Start the conversation