Membrane Finance ("Membrane") can block individual addresses, programs, contracts, and EOAs ("Accounts") from sending, receiving, minting, and redeeming EUROe on every blockchain on which EUROe is issued. This document outlines when and how Membrane denies access to the aforementioned functions and why Membrane reverses access denial.
To read more about the technical implications of access denial, please refer to our Developer Portal.
When Membrane Denies Access
Membrane will not deny access to Accounts except for when:
Receiving a request to do so from a competent government body, authority, or supervisory agency;
Receiving a request to do so from the owner & controller of an address, given sufficient proof; or
Membrane deems denying access necessary to comply with a law, regulation, or legal order from a recognised Finnish or EU authority.
How Membrane Denies Access
Membrane denies access to an Account by adding the Account to a denial list. Such events are recorded on the relevant blockchain and emit an event where applicable.
Reversals of Access Denials
Membrane may revert denial of access upon receiving a request from the same entity that initially issued the access denial request and after sufficiently validating the request with relevant authorities. Membrane's internal committees will approve all reversals prior to execution unless their access had originally been denied under section two of "When Membrane Denies Access".
Third-Party Access Denial
On certain blockchains, it is possible for an owner or another third party to deny access to an account or to its assets, for example, via deploying a smart contract that locks the assets from being used or accessed. If an account or the assets within that account have been blocked by the owner or a third party, Membrane will not be able to assist in the reversal of said blocking. Replacements for assets blocked by the owner or a third party will not be provided.