You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/evm/accounts.md
+12Lines changed: 12 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,18 @@ EOAs and Contract accounts function the same as on other EVM networks. Users may
22
22
23
23
However, in order to leverage all the features of Cadence, developers will need to utilize Cadence Owned Accounts.
24
24
25
+
:::danger
26
+
27
+
🚨🚨🚨 **ASSET LOSS RISK** 🚨🚨🚨
28
+
29
+
Cadence-Owned Accounts, easily identifiable by the leading zeroes (`0x00000000000000000000000`) **only exist on Flow**. The keys to these addresses are generated in a way that is not compatible with other networks.
30
+
31
+
As a result, any assets sent to one of these addresses on another network **will be lost permanently!**
32
+
33
+
We're working with major wallet providers to block such transfers, and recommend that all app and wallet developers do the same.
34
+
35
+
:::
36
+
25
37
## Cadence Owned Accounts
26
38
27
39
A Cadence Owned Account (COA) is a natively supported EVM smart contract wallet type that allows a Cadence resource to own and control an EVM address. This native wallet type provides the primitives needed to bridge or control assets across Flow EVM and Cadence facilitating composability between environments.
0 commit comments