Skip to content


pBridge is a bridge between several blockchains, which currently powers pSTAKE. This unique bridge enables transfer of value between multiple disparate blockchains such as Ethereum, Cosmos, Persistence etc.

pBridge ensures that transactions originating at the pSTAKE application end (Ethereum), pertaining to staking, unstaking, reward redemption, etc. are instantaneously executed at the protocol end of the native chain (e.g. Cosmos), namely: MsgSend, Delegate, Undelegate, Redeem Delegation Rewards etc. This enables seamless execution of PoS protocol transactions of native chains such as Cosmos, remote controlled from Ethereum smart contracts.

pBridge characteristics:

  • Fast Transactions: The inter-chain transactions are fairly fast, but they strictly follow the blockchain principles. This means that only after the transaction gets confirmed on one chain does it progress to send relevant transaction/s on the second chain. Hence, the transaction time will be roughly equal to the sum total of the average transaction confirmation times for the native chain and host chain (e.g. Cosmos and Ethereum respectively).

  • Decentralization: The bridge mechanism is also highly decentralized, which means it will be managed by multiple bridge validators. These bridge validators collectively maintain a single source of truth for pSTAKE.

  • Highest Level of Credibility: pBridge operations are secured by actual blockchain PoS validators (e.g. Cosmos network validators). This involves the safelisting of PoS validators which retain the highest level of credibility and performance, to be made participants of the bridge validator pool.

  • Economic Participation Based Security: Following the same principles of incentive-powered security protocols used by blockchains, pBridge also provides incentives for PoS validators to maintain the operation of the bridge. The users’ staking requests are delegated only to the participating validators in the pool, which can increase their returns from staking commissions significantly.

  • Crash Fault Tolerance: pBridge has a high crash fault tolerance mechanism baked into it due to the multi-validator approach. pBridge data is maintained in a distributed model of Apache Kafka message queue, providing the highest level of data availability. The validators also collectively participate in transaction signing for several chains.