1/N We're sorry to inform the community that an attacker was able to leverage a bug in our codebase and attack pBTC on BSC, stealing 277 BTC (most of its collateral).

The other bridges were not affected. All other funds in the pNetwork are safe.
2/N We have identified the bug and are working on fixing it. The bridges will be re-activated as soon as it's safe to, most likely in a matter of hours.

Updates to follow.
3/N To pTokens users. We are really sorry about what happened.

We are working on a solution for users who were affected by the attack (pBTC on BSC holders only). We will keep you posted on this.
4/N To the black hat hacker. Although this is a long shot, we're offering a clean $1,500,000 bounty if funds are returned.

Finding vulnerabilities is part of the game unfortunately, but we all want DeFi ecosystem to continue growing, returning funds is a step in that direction
5/N Status update: we have a proposed fix and we are now waiting for everyone to review it. We expect for the bridges to be back up in approximately 12 hours. We want to reassure everyone that we are prioritising security over speed.
6/N Status update: The bug on the pBTC on BSC bridge was identified and fixed. A detailed post-mortem will follow.

Bridges are being extensively reviewed for that and similar exploits. The bridges will be gradually reactivated over the next few days.
7/N The bridges will run with extra security measures in place for the first few days. This means slower transactions processing in exchange for higher security.

Updates to follow as the bridges go back up.
8/N Bridges:
- pBTC on EOS
- pBTC on Telos
- pLTC on EOS
are now back up and running with extra security measures in place for the first few days. You should expect longer than usual processing times.
9/N To pBTC on BSC holders. We are sorry about what happened and we want to reassure you that it's our priority to make you whole. In the meantime, pBTC on BSC is working as usual but is currently not redeemable as its bridge is suspended until further notice.

Updates to follow
10/N To pNetwork community. We're sorry about what happened & we appreciate the support we have received so far

Please bear w/ us during this difficult time. We'll all come back stronger. We'll keep you updated & give you the possibility to share feedback on how to move forward
11/N Status update: the pUOS on Ultra bridge was not affected and is now back up.

A detailed post-mortem will be shared tomorrow. Updates to follow on the gradual reactivation of all other bridges.
14/N Status update: additional bridges have been restarted, namely
pEOS-on-BSC
pBEP20-on-ETH
pTLOS-on-ETH
pBEP20-on-Polygon
pEOS-on-ETH
pEOS-on-Polygon
pERC20-on-BSC
pERC20-on-EOS
pERC20-on-Telos
pERC20-on-xDai
pTLOS-on-BSC
15/N Status update: all bridges are back and running as usual ๐Ÿ’ช

The pBTC-on-BSC bridge remains temporarily disabled while discussions on the compensation plan are ongoing
17/N New pNetwork DAO proposal is open ๐Ÿฆœ

โ“Should the DAO redirect DAO members' rewards for the current epoch (approx. 400k PNT) towards pBTC-on-BSC holders affected by the recent hack so as to enable them to join future DAO voting proposals?

Vote๐Ÿ‘‡
https://client.aragon.org/#/pnetwork/0x2211bfd97b1c02ae8ac305d206e9780ba7d8bff4/vote/12/
23a/N Status update: A new pNetwork DAO proposal is now open

โ“ Should the DAO recoup the value lost by pBTC-on-BSC holders affected by the recent hack via the 2-steps process (NFT sale + partial redirection of DAO member rewards) described in the Proposal 1 (rev0.6)?
23b/N๐Ÿ—ณ The voting proposal is open both on Ethereum and BSC. Cast your votes ๐Ÿ‘‡
- via Aragon (Ethereum) https://client.aragon.org/#/pnetwork/0x2211bfd97b1c02ae8ac305d206e9780ba7d8bff4/vote/13/
- via http://eidoo.app  (Ethereum)
- via Snapshot (BSC) https://snapshot.org/#/pnetwork-dao.eth/proposal/QmVmvQf3mnAFqRsiLjysCu5HYrU3H7tPtTz5FBAoAZy9KL
You can follow @pNetworkDeFi.
Tip: mention @twtextapp on a Twitter thread with the keyword โ€œunrollโ€ to get a link to it.

Latest Threads Unrolled: