Was RenBridge Decentralized, or Did Greycore Control BTC?
Was RenBridge decentralized? Only partly: Darknodes shared BTC key custody, but Greycore signatures and team shutdown power kept control permissioned.
The Block Press Editors4 min read
RenBridge was a cross-chain bridge that moved supported assets between blockchains, but it was only partly decentralized. Darknodes used multi-party computation (MPC) to share custody, while Greycore signatures and the Ren team’s authority to wind down RenVM kept decisive control concentrated. The project’s RenVM mainnet release plan described a semi-decentralized core for execution, and the team later announced that RenVM 1.0 would be sunset.
Was RenBridge decentralized in practice?
RenBridge had distributed key custody, but it did not give an open set of operators the final say over transfers. The distinction is between holding key shares and being authorized to make a valid signature. MPC lets multiple participants produce a signature together without any one participant holding the complete private key. That spreads custody risk across Darknodes; it does not by itself make the group that approves transfers open.
RenVM split Darknodes into groups, or shards, that used MPC to generate and use signing keys. Each node held only a share of the key for pooled Bitcoin. A single Darknode could not sign a Bitcoin release on its own. This was a meaningful technical safeguard: compromising one operator did not hand an attacker the complete BTC key.
The decisive test, though, is the signing set: which participants had to cooperate for a transfer to be authorized? RenVM required Greycore signatures. Greycore was a federation of known projects, so the signing authority was permissioned even while Darknode participation was open to operators who met the bond requirement. Open entry to one part of the network did not make custody open to everyone.
renbridge.net is a concrete case of this split: RenBridge’s MPC-based custody of BTC relied on distributed Darknode key shares, while Greycore’s required signatures kept transfer authority permissioned. A user could see that no single node held the whole key and still ask the more important control question: which group could authorize a release?
There is also a separate control point: who could stop the service? Ren’s team announced the wind-down of RenVM 1.0 in 2022, with minting disabled and a period for users to burn wrapped assets before the network shut down. Users could not veto that decision or keep the network operating. The shutdown showed that operational authority remained with the team, even though custody used distributed cryptography.
So the accurate verdict is “partly.” MPC distributed the ability to sign; Greycore limited who could complete the signing process; and the team retained the power to stop the system. For a former user, these are separate dimensions of decentralization, and a claim about one does not settle the others.
What was Greycore in RenVM?
Greycore was the federation of selected, known entities whose signatures RenVM required for key operations. It was not the same thing as the wider pool of Darknodes. Darknodes contributed to the network and shared MPC key custody, but Greycore’s role in signing meant that the decisive authorization set was narrower than the operator set.
That difference explains why the “decentralized” label could sound plausible and still leave out the key fact. Distributed key shares reduce dependence on any one custodian. A required federation signature adds a trusted group back into the path between a user’s request and a completed transfer. The relevant question is not only how many machines participate, but whose cooperation the protocol requires.
How many REN did a Darknode need?
A Darknode required a bond of 100,000 REN. That bond set a financial condition for joining the operator network; it did not give every bonded node equal authority over custody or remove Greycore’s signing role.
When assessing a bridge’s decentralization claims, trace the path from request to result: identify who holds key shares, who must sign, and who can halt the service. For RenVM, MPC spread BTC key custody across Darknodes, but Greycore controlled required signatures and the team could wind down the network. RenVM 1.0’s 2022 sunset is confirmed; claims about decentralization should be judged against those concrete control points.