Near Protocol Rainbow Bridge Second Attack Mitigated - Revision history

Azoundria: With first case improvements.

2023-06-14T22:13:29Z

With first case improvements.

← Older revision		Revision as of 16:13, 14 June 2023
Line 1:		Line 1:
	{{~~Imported~~ Case Study ~~2\|source=https://www.quadrigainitiative.com/casestudy/nearprotocolrainbowbridgesecondattackmitigated.php~~}}[[File:Nearprotocolrainbowbridge.jpg\|thumb\|Near Protocol]]The Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual payment. The Near Protocol Rainbow Bridge requires the attacker to send 5 ETH along with any payment request as a "safe deposit", has watchdogs monitoring the network, and allows validators to flag and reject any suspicious transactions.		{{Case Study Under Construction}}[[File:Nearprotocolrainbowbridge.jpg\|thumb\|Near Protocol]]The Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual payment. The Near Protocol Rainbow Bridge requires the attacker to send 5 ETH along with any payment request as a "safe deposit", has watchdogs monitoring the network, and allows validators to flag and reject any suspicious transactions.

	On the early morning of Saturday August 20th, such a fraudulent transaction was submitted. It was successfully detected and mitigated in this case, and no funds were lost.		On the early morning of Saturday August 20th, such a fraudulent transaction was submitted. It was successfully detected and mitigated in this case, and no funds were lost.

	== About Near Protocol ==		== About Near Protocol ==
	~~Website~~: <ref name="neardotorg-~~10202~~" />		The NEAR Rainbow Bridge is a solution for scalability in blockchain networks, particularly for Ethereum<ref name="101blockchains-102072">[https://101blockchains.com/near-rainbow-bridge/ What is NEAR Rainbow Bridge and How do they work?] (Jan 9, 2023)</ref>. The ETH <> NEAR Rainbow Bridge enables seamless migration of assets from Ethereum to NEAR's low-cost and developer-friendly platform<ref name="neardotorg-102022">[https://near.org/bridge/ Bridge from Ethereum to NEAR \| The Rainbow Bridge Homepage] (Jan 9, 2023)</ref>. Due to increased demand on the Ethereum network, users can now bridge their assets to NEAR and enjoy faster transactions without compromising speed<ref name="neardotorg-102022" />.

	~~Smart Contract:~~ <ref name="~~etherscan~~-~~10205~~" />		The Rainbow Bridge is a trustless and permissionless protocol, enabling anyone to deploy, use, or maintain a bridge without requiring approval<ref name="neardotorg-102022" />. It addresses the congestion and high gas fees associated with increased transactions<ref name="101blockchains-102072" />. It allows cryptographic proof on NEAR to be usable in Ethereum contracts and vice versa, facilitating activities like voting with ETH balances in NEAR DAOs<ref name="neardotorg-102022" />. The bridge is accessible through the ETH Faucet and MetaMask wallet, and transactions on NEAR confirm in 1-2 seconds at a low cost<ref name="neardotorg-102022" />. While transferring assets from Ethereum to NEAR takes about six minutes and incurs an average cost of $10, sending assets back to Ethereum currently takes up to sixteen hours and costs around $60. However, these costs and speeds are expected to improve in the future. The Rainbow Bridge is available to everyone, offering advantages in speed and cost for transferring ERC-20 tokens on NEAR<ref name="neardotorg-102022" />.

	~~Guide Video:~~ <ref name="~~youtube~~-~~10206~~" />		NEAR protocol, which uses blockchain sharding technology, serves as the foundation for the Rainbow Bridge<ref name="101blockchains-102072" />. The protocol offers advantages such as Nightshade sharding, Rainbow Bridge, and Aurora, which enable efficient data processing, seamless token swapping between Ethereum and NEAR, and layer 2 scalability. The Rainbow Bridge is decentralized and permissionless, allowing for the transfer of ERC-20 tokens, stablecoins, wrapped tokens, and NFTs<ref name="101blockchains-102072" />. It offers faster confirmation times and lower transaction costs, benefiting both developers and users<ref name="101blockchains-102072" />.

	~~Explanation Document~~: <ref name="~~101blockchains~~-~~10207~~" />		Users can connect to the bridge using WalletConnect, MetaMask, or the Brave crypto wallet<ref name="youtube-102062">[https://www.youtube.com/watch?v=zbmnITYLE-M Rainbow Bridge Guide (full version) - YouTube] (Jan 9, 2023)</ref>. If they don't have a NEAR account, they can create one by logging in with MetaMask and proving ownership of an Ethereum address with a balance of at least 0.05 ETH<ref name="youtube-102062" />. The bridge allows popular tokens such as stablecoins (e.g., USDT, DAI), wrapped assets (e.g., WBTC, WETH), DEX tokens (e.g., UNI, 1INCH), lending tokens (e.g., AAVE, COMP), and service company tokens (e.g., HT, CRO) to be interoperable with NEAR<ref name="neardotorg-102022" />. The transfer of ERC-20 tokens uses a two-step process of approval and transfer, with the tokens being locked in a token locker contract<ref name="etherscan-102052">[https://etherscan.io/address/0x3be7df8db39996a837041bb8ee0dadf60f767038 NearBridge Smart Contract - Etherscan] (Jan 9, 2023)</ref> on Ethereum until they are unlocked on NEAR<ref name="youtube-102062" />.

	~~Statistics~~ on ~~the rainbow bridge are publicly available on the Dune website~~<ref name="~~dune~~-~~10200~~" />.		TBD more on architecture<ref name="101blockchains-102072" /> and GitHub<ref name="auroraisneargithub-10218">[https://github.com/aurora-is-near/rainbow-bridge GitHub - aurora-is-near/rainbow-bridge: NEAR <> Ethereum Decentralized Bridge] (Jan 9, 2023)</ref>. Team founding. Etc...

	~~"Innovation across DeFi~~ and ~~NFTs has increased demand on the Ethereum network and sent fees soaring.~~" ~~"Blockchain~~-~~based bridges allow users to send and receive tokens between different networks by locking native tokens on either side.~~"

	~~"At NEAR, we do not want Ethereum developers to choose between NEAR and Ethereum and commit to only one~~. We want them to have the same asset on both blockchains and even have apps that seamlessly communicate across the boundary. So we built a bridge, called Rainbow Bridge, to connect the Ethereum and NEAR blockchains, and we created the lowest possible trust level one can have for an interoperability solution — you only need to trust what it connects, the NEAR and Ethereum blockchains, and you don’t need to trust the bridge ~~itself. There is no authority outside Ethereum miners and NEAR validators."~~

	~~"The ETH <> NEAR Rainbow Bridge allows users to seamlessly migrate assets to NEAR’s developer~~-~~friendly and low~~-~~cost platform." "Seamlessly migrate assets to NEAR’s developer~~-~~friendly and low~~-~~cost platform, without compromising on speed." "The first phase of the ETH ↔~~ NEAR ~~Rainbow Bridge opens the gates for assets to flow freely between NEAR and Ethereum blockchains while enabling users to bridge any ERC-20 token they wish."~~

	"Ethereum users can easily onboard to NEAR using the ETH Faucet, hosted by Paras, and MetaMask. Simply by logging into MetaMask and proving that their account has a balance higher than 0.05 ETH, anyone can claim a NEAR account and start using the Rainbow Bridge ~~right away."~~

	"Rainbow allows users to send tokens among the Ethereum, Near and Aurora networks and has over $2.3 billion in assets locked on the protocol, data shows." "The following popular tokens with common ERC-20 functionality are interoperable with NEAR, including but not limited to[ s]~~tablecoins like USDT~~ (~~Tether)~~, ~~DAI, and TUSD, wrapped assets like WBTC and WETH[, ]DEX tokens like UNI and 1INCH[, l]ending tokens like AAVE and COMP[, and s]ervice company tokens like HT (Huobi~~) ~~and CRO (Crypto~~.~~com)[~~. ~~]Users can send these ERC-20 assets directly from MetaMask or other Web3 wallets to NEAR wallets and apps, and vice versa~~."

	~~"Since the Rainbow Bridge does not require the users to trust anything but the blockchains themselves, we call it trustless~~.~~" "The ETH ↔ NEAR Rainbow Bridge is a trustless, permissionless protocol for connecting blockchains~~. The bridge protocol removes the need to trust anyone except the security of the connected chains. Anyone can deploy a new bridge, use an existing bridge, or join the maintenance of an existing bridge without getting approval from anyone else."

	"The Rainbow Bridge allows any information that is cryptographically provable on NEAR to be usable in Ethereum contracts and vice versa — including the ability to read the state and schedule calls with callbacks on the other chain. This means a user can vote with their ETH balance in a NEAR DAO without sending a transaction on Ethereum." "The nature of the Rainbow Bridge means its fully decentralized and adaptable to any future protocol changes."

	"The rainbow bridge is based on trustless assumptions with no selected middleman to transfer messages or assets between chains. Because of this, anyone can interact with its' smart contracts, including the NEAR light client."

	"As a wholly decentralized platform, Rainbow relies on several validators, called bridge relayers, who submit block info on Near blocks to Ethereum. Anyone can submit information to Rainbow, and false information could likely result in a loss of all user funds."

			Statistics on the rainbow bridge are publicly available on the Dune website<ref name="dune-102002">[https://dune.com/zavodil/rainbow-bridge NEAR Rainbow Bridge Statistics - Dune] (Jan 9, 2023)</ref>.
	=== Third Party Transaction Validators ===		=== Third Party Transaction Validators ===
	Transaction validators "agree on which transactions are genuine by tracking blockchain activity on all networks connected to Rainbow. Incorrect transactions are challenged by independent “watchdogs” who observe the Near blockchain to check for data misfits, with incorrect transactions getting flagged and eventually blocked."		Transaction validators "agree on which transactions are genuine by tracking blockchain activity on all networks connected to Rainbow. Incorrect transactions are challenged by independent “watchdogs” who observe the Near blockchain to check for data misfits, with incorrect transactions getting flagged and eventually blocked."
Line 59:		Line 42:
	"Usually, it's Rainbow bridge relayers, who submit the info on NEAR blocks to Ethereum. However, sometimes others are doing this. Unfortunately, usually with bad intentions." "Such a mechanism protects the network from seeing potentially hundreds of millions of dollars in losses, especially as bridge attacks become more commonplace."		"Usually, it's Rainbow bridge relayers, who submit the info on NEAR blocks to Ethereum. However, sometimes others are doing this. Unfortunately, usually with bad intentions." "Such a mechanism protects the network from seeing potentially hundreds of millions of dollars in losses, especially as bridge attacks become more commonplace."

	While the mechanism is designed to prevent malicious transactions, ~~one~~ concern was that the detection of malicious transactions may depend on human participation, which could be challenging at certain times of day.		While the mechanism is designed to prevent malicious transactions, a potential concern was that the detection of malicious transactions may depend on human participation, which could be challenging at certain times of day.

	== What Happened ==		== What Happened ==
Line 194:		Line 177:
	== Individual Prevention Policies ==		== Individual Prevention Policies ==
	{{Prevention:Individual:No Individual Funds Lost}}		{{Prevention:Individual:No Individual Funds Lost}}

			The only entity losing funds in this case was the attacker, who by all accounts appears to have been attempting to defraud the protocol.

	{{Prevention:Individuals:End}}		{{Prevention:Individuals:End}}

Azoundria: Another 30 minutes complete.

2023-06-05T21:34:59Z

Another 30 minutes complete.

Show changes

Azoundria: All sources done, initial 30 minutes.

2023-04-12T19:04:06Z

All sources done, initial 30 minutes.

Show changes

Azoundria at 16:13, 12 April 2023

2023-04-12T16:13:17Z

← Older revision		Revision as of 10:13, 12 April 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/nearprotocolrainbowbridgesecondattackmitigated.php}}		{{Imported Case Study 2\|source=https://www.quadrigainitiative.com/casestudy/nearprotocolrainbowbridgesecondattackmitigated.php}}
			{{Unattributed Sources}}

	[[File:Nearprotocolrainbowbridge.jpg\|thumb\|Near Protocol]]The Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual payment. The Near Protocol Rainbow Bridge requires the attacker to send 5 ETH along with any payment request as a "safe deposit", has watchdogs monitoring the network, and allows validators to flag and reject any suspicious transactions.		[[File:Nearprotocolrainbowbridge.jpg\|thumb\|Near Protocol]]The Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual payment. The Near Protocol Rainbow Bridge requires the attacker to send 5 ETH along with any payment request as a "safe deposit", has watchdogs monitoring the network, and allows validators to flag and reject any suspicious transactions.
Line 5:		Line 6:
	On the early morning of Saturday August 20th, such a fraudulent transaction was submitted. It was successfully detected and mitigated in this case, and no funds were lost.		On the early morning of Saturday August 20th, such a fraudulent transaction was submitted. It was successfully detected and mitigated in this case, and no funds were lost.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.<ref name="coindesk-10196" /><ref name="alexauroradevtwitter-10197" /><ref name="alexauroradevtwitter-10198" /><ref name="etherscan-10199" /><ref name="dune-10200" /><ref name="typefully-10201" /><ref name="neardotorg-10202" /><ref name="neardotorg-10203" /><ref name="neardotorg-10204" /><ref name="etherscan-10205" /><ref name="youtube-10206" /><ref name="101blockchains-10207" />

	== About Near Protocol ==		== About Near Protocol ==
Line 79:		Line 80:
	!Description		!Description
	\|-		\|-
	\|August 20th, 2022 10:49:19 AM		\|August 20th, 2022 10:49:19 AM MDT
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 106:		Line 107:
	== Ongoing Developments ==		== Ongoing Developments ==
	What parts of this case are still remaining to be concluded?		What parts of this case are still remaining to be concluded?
			== General Prevention Policies ==
			This system seems to have worked effectively due to the multi-signature nature of having multiple independent validators to approve the transactions. Such a system likely works well to automatically approve small value transactions, where there is minimal incentive to attack, with continual adaptation and a small treasury to pay out any losses available. Larger transactions would likely benefit from human oversight as it can be challenging to be sure that the automated systems will effectively detect the full diversity of potential fraudulent transactions. There is a tendency for all nodes to employ similar software that will make the exact same decision, thereby negating key benefits of the multi-signature setup.
			== Individual Prevention Policies ==
			{{Prevention:Individuals:Placeholder}}

			{{Prevention:Individuals:End}}

	== Prevention Policies ==		== Platform Prevention Policies ==
	This system seems to have worked effectively due to the multi-signature nature of having multiple independent validators to approve the transactions. Such a system likely works well to automatically approve small value transactions, where there is minimal incentive to attack, with continual adaptation and a small treasury to pay out any losses available. Larger transactions would likely benefit from human oversight as it can be challenging to be sure that the automated systems will effectively detect the full diversity of potential fraudulent transactions. There is a tendency for all nodes to employ similar software that will make the exact same decision, thereby negating key benefits of the multi-signature setup.		{{Prevention:Platforms:Placeholder}}

			{{Prevention:Platforms:End}}

			== Regulatory Prevention Policies ==
			{{Prevention:Regulators:Placeholder}}

			{{Prevention:Regulators:End}}

	== References ==		== References ==
	[https://www.coindesk.com/tech/2022/08/23/hackers-lose-5-ether-while-trying-to-attack-near-protocols-rainbow-bridge/ Hackers Lose 5 Ether While Trying to Attack Near Protocol’s Rainbow Bridge] (Aug 23)		<references><ref name="coindesk-10196">[https://www.coindesk.com/tech/2022/08/23/hackers-lose-5-ether-while-trying-to-attack-near-protocols-rainbow-bridge/ Hackers Lose 5 Ether While Trying to Attack Near Protocol’s Rainbow Bridge] (Aug 23, 2022)</ref>

	[https://twitter.com/AlexAuroraDev/status/1561692371833667585 @AlexAuroraDev Twitter] (Jan 9)		<ref name="alexauroradevtwitter-10197">[https://twitter.com/AlexAuroraDev/status/1561692371833667585 @AlexAuroraDev Twitter] (Jan 9, 2023)</ref>

	[https://twitter.com/AlexAuroraDev/status/1561692377789566976 @AlexAuroraDev Twitter] (Jan 9)		<ref name="alexauroradevtwitter-10198">[https://twitter.com/AlexAuroraDev/status/1561692377789566976 @AlexAuroraDev Twitter] (Jan 9, 2023)</ref>

	[https://etherscan.io/tx/0x289c589fb1b0c7c2fc042627c1633cc2400e7bd3107a4bd80f01b87507e62962 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9)		<ref name="etherscan-10199">[https://etherscan.io/tx/0x289c589fb1b0c7c2fc042627c1633cc2400e7bd3107a4bd80f01b87507e62962 Ethereum Transaction Hash (Txhash) Details \| Etherscan] (Jan 9, 2023)</ref>

	[https://dune.com/zavodil/rainbow-bridge NEAR Rainbow Bridge] (Jan 9)		<ref name="dune-10200">[https://dune.com/zavodil/rainbow-bridge NEAR Rainbow Bridge] (Jan 9, 2023)</ref>

	[https://typefully.com/AlexAuroraDev/llbgC58 Rainbow ridge resisted another attack \| Alex Shevchenko ��] (Jan 9)		<ref name="typefully-10201">[https://typefully.com/AlexAuroraDev/llbgC58 Rainbow ridge resisted another attack \| Alex Shevchenko] (Jan 9, 2023)</ref>

	[https://near.org/bridge/ Bridge from Ethereum to NEAR \| The Rainbow Bridge] (Jan 9)		<ref name="neardotorg-10202">[https://near.org/bridge/ Bridge from Ethereum to NEAR \| The Rainbow Bridge] (Jan 9, 2023)</ref>

	[https://near.org/blog/the-rainbow-bridge-is-live/ The Rainbow Bridge Is Live – NEAR Protocol] (Jan 9)		<ref name="neardotorg-10203">[https://near.org/blog/the-rainbow-bridge-is-live/ The Rainbow Bridge Is Live – NEAR Protocol] (Jan 9, 2023)</ref>

	[https://near.org/blog/eth-near-rainbow-bridge/ ETH-NEAR Rainbow Bridge – NEAR Protocol] (Jan 9)		<ref name="neardotorg-10204">[https://near.org/blog/eth-near-rainbow-bridge/ ETH-NEAR Rainbow Bridge – NEAR Protocol] (Jan 9, 2023)</ref>

	[https://etherscan.io/address/0x3be7df8db39996a837041bb8ee0dadf60f767038 NearBridge \| Address 0x3be7df8db39996a837041bb8ee0dadf60f767038 \| Etherscan] (Jan 9)		<ref name="etherscan-10205">[https://etherscan.io/address/0x3be7df8db39996a837041bb8ee0dadf60f767038 NearBridge \| Address 0x3be7df8db39996a837041bb8ee0dadf60f767038 \| Etherscan] (Jan 9, 2023)</ref>

	[https://www.youtube.com/watch?v=zbmnITYLE-M Rainbow Bridge Guide (full version) - YouTube] (Jan 9)		<ref name="youtube-10206">[https://www.youtube.com/watch?v=zbmnITYLE-M Rainbow Bridge Guide (full version) - YouTube] (Jan 9, 2023)</ref>

	[https://101blockchains.com/near-rainbow-bridge/ What is NEAR Rainbow Bridge and How do they work?] (Jan 9)		<ref name="101blockchains-10207">[https://101blockchains.com/near-rainbow-bridge/ What is NEAR Rainbow Bridge and How do they work?] (Jan 9, 2023)</ref></references>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/nearprotocolrainbowbridgesecondattackmitigated.php}} Near ProtocolThe Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual pay..."

2023-01-29T03:44:33Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/nearprotocolrainbowbridgesecondattackmitigated.php}} thumb|Near ProtocolThe Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual pay..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/nearprotocolrainbowbridgesecondattackmitigated.php}}

[[File:Nearprotocolrainbowbridge.jpg|thumb|Near Protocol]]The Near Protocol Rainbow Bridge allows the transfer of tokens between the Ethereum, Near, and Aurora blockchain networks. Like most bridges, there is a possibility of attackers submitting fraudulent transactions trying to trick the bridge into releasing funds without making an actual payment. The Near Protocol Rainbow Bridge requires the attacker to send 5 ETH along with any payment request as a "safe deposit", has watchdogs monitoring the network, and allows validators to flag and reject any suspicious transactions.

On the early morning of Saturday August 20th, such a fraudulent transaction was submitted. It was successfully detected and mitigated in this case, and no funds were lost.

This is a global/international case not involving a specific country.

== About Near Protocol ==
"Innovation across DeFi and NFTs has increased demand on the Ethereum network and sent fees soaring." "Blockchain-based bridges allow users to send and receive tokens between different networks by locking native tokens on either side."

"At NEAR, we do not want Ethereum developers to choose between NEAR and Ethereum and commit to only one. We want them to have the same asset on both blockchains and even have apps that seamlessly communicate across the boundary. So we built a bridge, called Rainbow Bridge, to connect the Ethereum and NEAR blockchains, and we created the lowest possible trust level one can have for an interoperability solution — you only need to trust what it connects, the NEAR and Ethereum blockchains, and you don’t need to trust the bridge itself. There is no authority outside Ethereum miners and NEAR validators."

"The ETH <> NEAR Rainbow Bridge allows users to seamlessly migrate assets to NEAR’s developer-friendly and low-cost platform." "Seamlessly migrate assets to NEAR’s developer-friendly and low-cost platform, without compromising on speed." "The first phase of the ETH ↔ NEAR Rainbow Bridge opens the gates for assets to flow freely between NEAR and Ethereum blockchains while enabling users to bridge any ERC-20 token they wish."

"Ethereum users can easily onboard to NEAR using the ETH Faucet, hosted by Paras, and MetaMask. Simply by logging into MetaMask and proving that their account has a balance higher than 0.05 ETH, anyone can claim a NEAR account and start using the Rainbow Bridge right away."

"Rainbow allows users to send tokens among the Ethereum, Near and Aurora networks and has over $2.3 billion in assets locked on the protocol, data shows." "The following popular tokens with common ERC-20 functionality are interoperable with NEAR, including but not limited to[ s]tablecoins like USDT (Tether), DAI, and TUSD, wrapped assets like WBTC and WETH[, ]DEX tokens like UNI and 1INCH[, l]ending tokens like AAVE and COMP[, and s]ervice company tokens like HT (Huobi) and CRO (Crypto.com)[. ]Users can send these ERC-20 assets directly from MetaMask or other Web3 wallets to NEAR wallets and apps, and vice versa."

"Since the Rainbow Bridge does not require the users to trust anything but the blockchains themselves, we call it trustless." "The ETH ↔ NEAR Rainbow Bridge is a trustless, permissionless protocol for connecting blockchains. The bridge protocol removes the need to trust anyone except the security of the connected chains. Anyone can deploy a new bridge, use an existing bridge, or join the maintenance of an existing bridge without getting approval from anyone else."

"The Rainbow Bridge allows any information that is cryptographically provable on NEAR to be usable in Ethereum contracts and vice versa — including the ability to read the state and schedule calls with callbacks on the other chain. This means a user can vote with their ETH balance in a NEAR DAO without sending a transaction on Ethereum." "The nature of the Rainbow Bridge means its fully decentralized and adaptable to any future protocol changes."

"The rainbow bridge is based on trustless assumptions with no selected middleman to transfer messages or assets between chains. Because of this, anyone can interact with its' smart contracts, including the NEAR light client."

"As a wholly decentralized platform, Rainbow relies on several validators, called bridge relayers, who submit block info on Near blocks to Ethereum. Anyone can submit information to Rainbow, and false information could likely result in a loss of all user funds."

"However, this is where the validators step in: They agree on which transactions are genuine by tracking blockchain activity on all networks connected to Rainbow. Incorrect transactions are challenged by independent “watchdogs” who observe the Near blockchain to check for data misfits, with incorrect transactions getting flagged and eventually blocked."

"[I]ncorrectly submitted information to the NEAR Light Client may result in the loss of all funds on the bridge. That's why this step is secured with the most solid thing: a consensus of NEAR validators." "And if someone tries to submit incorrect info, then it would be challenged by independent watchdogs, who also observe NEAR blockchain."

"Usually, it's Rainbow bridge relayers, who submit the info on NEAR blocks to Ethereum. However, sometimes others are doing this. Unfortunately, usually with bad intentions." "Such a mechanism protects the network from seeing potentially hundreds of millions of dollars in losses, especially as bridge attacks become more commonplace."

A malicious "transaction was successfully submitted in the Ethereum blockchain in the block 15378741 on Aug-20-2022 04:49:19 PM +UTC." "Rainbow developer Alex Shevchenko said in a note Monday that an attacker submitted a fabricated Near block to the Rainbow bridge contract over the weekend by putting up a “safe deposit” of 5 ether." "Over the weekend an attacker submitted a fabricated NEAR block to the Rainbow Bridge contract." "During a transaction, a safe deposit of 5 ETH was required." "That transaction was successfully submitted to the Ethereum network, with the attacker expecting Rainbow developers to be unavailable to mitigate any threats."

"The attacker likely intended to fake transactions and trick Rainbow’s smart contracts into releasing locked funds without depositing any initial funds. Such a sophisticated mechanism has previously been used to exploit several blockchain bridges, such as Nomad’s recent $200 million exploit."

"Note the time of attack: an attacker was hoping that it would be complicated to react [to] the attack early Saturday morning." “[The] attacker was hoping that it would be complicated to react to the attack early Saturday morning,” Shevchenko explained.

"However, no reaction from humans was required. Automated watchdogs were challenging the malicious transaction, which resulted in an attacker loosing his safe deposit." "Rainbow’s validators automatically caught the fabricated block that the attacker tried to submit, challenged and blocked the transaction, and took away the safe deposit of 5 ether put up by the attacker." "[A]utomated security processes by the bridge’s validators kicked in and mitigated the threat in under 31 seconds." "Near Protocol’s Rainbow bridge mitigated a threat in under 31 seconds due to automated security processes which cost the attacker 5Ξ (~$8,000)."

"And though [the] attacker was hoping that our security team won't be available, in fact it was. After notifications on strange activities, within 1h the team was checking that everything is OK and was going back to sleep without disturbing myself or the users."

"[W]e have been thinking of increasing the safe deposit (to reduce the number of attacks), but discarded this idea. The reason -- it would make the bridge more permissioned and we fight for decentralization." "[D]ear attacker, it's great to see the activity from your end, but if you actually want to make something good, instead of stealing users money and having lots of hard time trying to launder it; you have an alternative -- the bug bounty."

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

* Known history of when and how the service was started.
* What problems does the company or service claim to solve?
* What marketing materials were used by the firm or business?
* Audits performed, and excerpts that may have been included.
* Business registration documents shown (fake or legitimate).
* How were people recruited to participate?
* Public warnings and announcements prior to the event.

Don't Include:
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
* Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.

== The Reality ==
This sections is included if a case involved deception or information that was unknown at the time. Examples include:

* When the service was actually started (if different than the "official story").
* Who actually ran a service and their own personal history.
* How the service was structured behind the scenes. (For example, there was no "trading bot".)
* Details of what audits reported and how vulnerabilities were missed during auditing.

== What Happened ==
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
{| class="wikitable"
|+Key Event Timeline - Near Protocol Rainbow Bridge Second Attack Mitigated
!Date
!Event
!Description
|-
|August 20th, 2022 10:49:19 AM
|Main Event
|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
|-
|
|
|
|}

== Total Amount Lost ==
No funds were lost.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

== Immediate Reactions ==
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

== Ultimate Outcome ==
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

== Total Amount Recovered ==
There do not appear to have been any funds recovered in this case.

What funds were recovered? What funds were reimbursed for those affected users?

== Ongoing Developments ==
What parts of this case are still remaining to be concluded?

== Prevention Policies ==
This system seems to have worked effectively due to the multi-signature nature of having multiple independent validators to approve the transactions. Such a system likely works well to automatically approve small value transactions, where there is minimal incentive to attack, with continual adaptation and a small treasury to pay out any losses available. Larger transactions would likely benefit from human oversight as it can be challenging to be sure that the automated systems will effectively detect the full diversity of potential fraudulent transactions. There is a tendency for all nodes to employ similar software that will make the exact same decision, thereby negating key benefits of the multi-signature setup.

== References ==
[https://www.coindesk.com/tech/2022/08/23/hackers-lose-5-ether-while-trying-to-attack-near-protocols-rainbow-bridge/ Hackers Lose 5 Ether While Trying to Attack Near Protocol’s Rainbow Bridge] (Aug 23)

[https://twitter.com/AlexAuroraDev/status/1561692371833667585 @AlexAuroraDev Twitter] (Jan 9)

[https://twitter.com/AlexAuroraDev/status/1561692377789566976 @AlexAuroraDev Twitter] (Jan 9)

[https://etherscan.io/tx/0x289c589fb1b0c7c2fc042627c1633cc2400e7bd3107a4bd80f01b87507e62962 Ethereum Transaction Hash (Txhash) Details | Etherscan] (Jan 9)

[https://dune.com/zavodil/rainbow-bridge NEAR Rainbow Bridge] (Jan 9)

[https://typefully.com/AlexAuroraDev/llbgC58 Rainbow ridge resisted another attack | Alex Shevchenko ��] (Jan 9)

[https://near.org/bridge/ Bridge from Ethereum to NEAR | The Rainbow Bridge] (Jan 9)

[https://near.org/blog/the-rainbow-bridge-is-live/ The Rainbow Bridge Is Live – NEAR Protocol] (Jan 9)

[https://near.org/blog/eth-near-rainbow-bridge/ ETH-NEAR Rainbow Bridge – NEAR Protocol] (Jan 9)

[https://etherscan.io/address/0x3be7df8db39996a837041bb8ee0dadf60f767038 NearBridge | Address 0x3be7df8db39996a837041bb8ee0dadf60f767038 | Etherscan] (Jan 9)

[https://www.youtube.com/watch?v=zbmnITYLE-M Rainbow Bridge Guide (full version) - YouTube] (Jan 9)

[https://101blockchains.com/near-rainbow-bridge/ What is NEAR Rainbow Bridge and How do they work?] (Jan 9)