Oasis runs several environments side by side on one network, and they do not share an address format. Emerald is the Ethereum-style one, where addresses start with 0x.
Your staking, though, does not happen on Emerald. It happens on the network's underlying layer, under an address starting oasis1, and a wallet import of Emerald alone will not see it.
Fees across all of it are paid in ROSE.
What you get out of the box
Pick your import method.
On Oasis
- For Emerald, copy your address starting 0x.
- For staking, copy your address starting oasis1. It is a different format and holds a history the 0x address does not show.
On Kryptos
- Go to Kryptos.io and sign up with your Google account.
- From the menu, click Integrations.
- Click Add Integration and search for Oasis Emerald.
- Click the Oasis Emerald icon, then choose Import using Address.
- Give the wallet a name, paste your address, and click Import Your Transactions.
Good to know
- Staking rewards arrive on the oasis1 address, not on Emerald.
- Moving ROSE between the layers is a deposit or withdrawal between your own addresses, not a trade.
- Emerald has very little activity left. Sapphire, the confidential environment alongside it, is the busier one.
Several environments, one network, two address formats
Oasis is built differently from most networks, and the difference decides what you need to import.
Underneath there is a base layer that handles consensus and staking. On top of it run separate environments for different purposes. Emerald is the Ethereum-compatible, transparent one, with addresses starting 0x. Sapphire is its confidential sibling, also using 0x addresses, where contract activity is encrypted. The base layer uses a different format entirely, starting oasis1.
The consequence people run into is that staking is not on Emerald. It happens on the base layer, so rewards arrive at an oasis1 address that a wallet showing your 0x address will never display. Somebody who has delegated ROSE for a year and imports only Emerald will find no staking income whatsoever, and reasonably conclude something is broken.
Moving ROSE between the layers is a deposit or a withdrawal. It is your own asset moving between your own addresses, so nothing was sold, but it appears on two separate ledgers in two different formats and needs both sides present to pair up.
The confidential environment adds a further limit worth knowing about in advance. Because contract activity there is encrypted, reading an address tells you that a transaction happened and what it cost in gas, but not what was exchanged. That is the point of the design, and it means positions held there generally have to be exported from the application rather than reconstructed from the chain.
One practical note on Emerald specifically: both its value and its activity have fallen to very little, and it has experienced periods of not producing blocks. If your import comes back nearly empty, that may be an accurate picture. For how transfers between your own wallets are treated, see the USA crypto tax guide or the UK crypto tax guide.
Manage your Oasis Emerald portfolio with Kryptos.
Finding staking rewards that are not on Emerald
Staking happens on the network's underlying layer under a different address. Importing only your 0x address misses it entirely.
Moving ROSE between layers
Deposits and withdrawals between the two are transfers of your own assets, though they appear on two different ledgers.
Understanding what a confidential environment hides
The sibling environment encrypts what contracts do, so an address import there sees far less than on a transparent chain.
Audit-ready, automatically.
Once your wallets and exchanges are connected, generating a tax report takes a single click. Open Reports from the menu, choose your jurisdiction, and download.
Your staking history is on a different address
Rewards from delegation arrive on the oasis1 address rather than on Emerald. A report built only from the 0x address will show no staking income at all.
Moving between layers is not a disposal
Depositing ROSE from the underlying layer onto Emerald, or withdrawing it back, moves your own asset between your own addresses. It leaves records on two ledgers for one movement.
Confidential environments limit what can be imported
Where contract activity is encrypted, an address import can see that something happened and what gas it cost, but not what was exchanged. Those positions usually need exporting from the application itself.
Emerald is very quiet now
Activity and value on Emerald have fallen to very little. If an import returns almost nothing, that may be accurate rather than a failure.
Read-only by design.
- Kryptos only ever needs your public wallet address
- A public address is read-only. It can't move or spend anything
- We never ask for your recovery phrase or private key
- Remove a wallet whenever you like, and its data goes with it
If something doesn't sync.
They are on your oasis1 address, not on Emerald. Add that as well.
It probably came from the underlying layer. Import that address and the two sides pair up.
Emerald has very little activity left. Check whether your positions are on the confidential environment instead.
Still stuck? Email support@kryptos.io or open live chat from the app.