Created by https://github.com/oasisprotocol/wallet/blob/master/.github/workflows/dump-validators.yml

If CI actions and checks don't run in this PR: close it and reopen.
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#triggering-further-workflow-runs

Fixes #2150 and #2151

Before

After

Fixes #2123 (review)

Fixes yarn test:screenshots, broken since d3d1af0.

Screenshots failing in monthly CI: https://github.com/oasisprotocol/wallet/actions/runs/13598927233/job/38021610407

Related to #2132

Extensions don't send origin/referrer header when loading iframe and transak now
responds with Referrer-Policy: same-origin; X-Frame-Options: sameorigin;.

We embed transak based on window size, so transak could get embedded and fail if
user opens the extension in a large tab. This mitigates a failure in 5 seconds.

Including the https://wallet.prd.oasis.io production URL when checking the origin. This is similar to what we already do for Oasis Explorer, which has https://explorer.oasis.io and https://explorer.prd.oasis.io. Similarly, we add the corresponding environment variables, update deploy URLs, and refine conditions for displaying the "this is not a production deploy" banner.

Closes #2141

Looks like extensions don't send origin/referrer header when loading iframe and transak now responds with Referrer-Policy: same-origin; X-Frame-Options: sameorigin;

Luckily our extension does not embed transak, but opens it in a new tab. Mobile app too, except maybe on tablets. Not sure if iframe would load in a mobile app context

Closes #2143

Sleeker UX for first-time users/ROFL developers.

Partial fix for #384

Fixes #10

Fixes #385

Partial fix for #384

oa@matevz-oa:~/demo-rofl-chatbot$ oasis rofl deploy
To deploy your ROFL app, you can decide between one of the two options:

A. RUN YOUR OWN OASIS NODE

   1. Follow https://docs.oasis.io/node/run-your-node/paratime-client-node
      and configure your TDX Oasis node
   2. Copy demo-rofl-chatbot.default.orc to your node, for example /node/rofls/
   3. Add the following snippet to your config.yml:

      runtime:
        paths:
          - /node/rofls/demo-rofl-chatbot.default.orc

   4. Restart your node

B. DEPLOY YOUR ROFL TO THE OASIS PROVIDER

   1. Upload demo-rofl-chatbot.default.orc to a publicly accessible file server.
   2. Reach out to us at https://oasis.io/discord #dev-central channel and we
      will run your ROFL app inside the TEE on our servers.

Fixes #398

Based on #391
Fixes #375

This fixes an issue when fetching metadata for Rust packages which are part of workspaces since in those cases cargo metadata returns information about all packages in the workspace instead of just the package in the current working directory.

Running oasis rofl build now updates the manifest by default. Pass --no-update-manifest if you really don't want to update it. Mark --update-manifest as deprecated until all the examples and demos are updated to avoid breaking compatibility.

Detect docker-compose.yml, docker-compose.yaml, compose.yml if they already exist on oasis rofl init. Useful, if you want to ROFLize existing containers.

Partial fix for #384

In some projects, we needed to separate between the generic compose.yaml files and ROFL-tailored compose files (e.g. how env variables are populated). In this case we named it rofl-compose.yaml. When running oasis rofl init, autodetect it and use it, if it exists.

Fixes: #807

Fixes: #938

Supports roflmarket transactions and events.

• adds admin_eth address to rofl app response (if known)
• optimize rofl instance transactions query

testnet pontusxdev and pontusxtest are both similar to sapphire. For now, the same names addresses are also valid there.

This commit adds the corresponding JSON lists.
(Which are simply copies for the one for Sapphire.)

By default pgxpool uses a very conservative limit for maximum number of connections (max(num_cpu's, 4)). We make this configurable, and also bump the default to 10.

In production we probably want to bump this to something like 50 or 100.

Minor release with a couple of fixes.

As mentioned in https://github.com/oasisprotocol/nexus/pull/929/files#r2009079229

No need to provide a config option for this, as it can be specified in the db connection string.

Fixes: #932

This should be good enough since we only use env variables for a couple of config settings (none of those should have commas unless providing a list of values).

The Nexus Sapphire Testnet analyzer got stuck at processing block 10653792 that includes the new recently added InstanceRegisteredEvent (oasisprotocol/oasis-sdk#2159). This PR adds support for decoding such events that was missing in #917.

{"analyzer":"sapphire","caller":"block.go:412","height":10653792,"level":"info","mode":"slow-sync","module":"analysis_service","msg":"processing block","ts":"2025-03-05T18:00:43.160965827Z"}
{"analyzer":"sapphire","caller":"block.go:425","err":"extract non-tx events: event 6: decode rofl: invalid rofl event code: 4; raw event: {Module:rofl Code:4 Value:[129 162 99 114 97 107 161 103 101 100 50 53 53 49 57 88 32 22 23 122 67 18 40 176 86 9 150 65 237 63 79 58 186 10 247 12 51 163 118 159 50 118 57 28 89 227 17 215 75 102 97 112 112 95 105 100 85 0 215 149 192 51 251 75 148 135 61 129 182 50 127 83 113 118 143 252 111 207] TxHash:41ba7d12683a75b590f72e33b16c9979d92ce9a3d5caf4c177e36e885b432dcb}","height":10653792,"level":"error","mode":"slow-sync","module":"analysis_service","msg":"error processing block","ts":"2025-03-05T18:00:43.161497176Z"}

After applying this hotfix the Nexus Sapphire Testnet analyzer works again.

oasisprotocol/explorer#1847

Just a sanity filter.

Related to #820

Decision made during sync meeting

Extracted from #1777

API is not deployed yet, but we have almost everything to render ROFL apps list page (except last activity timestamp)

Extracted from #1777

• add ROFL status component
• clean up badge usage a little bit by creating a common StatusBadge component
• add Storybook

Storybook:

Adds the ability to switch between distance(age) and date-time view on tables.

Closes #1700

Extracted from #1777

• instances card needed for incoming ROFL app details page (RAK column will link to another view one day)
• API bindings sync

preview with mocked data

We might want to add other local options which are stored on LocalStorage, and changed based on used input.

The infrastructure added for TableConfig is perfect for all similar settings, just needs a more fitting name.

This provides the base for:

• #1794

Extracted from #1777

• looks like ROFL link logic is almost the same as validator link
• shared stuff moved to Link component. In the future this component should handle all links (as long as it is possible)

ROFL links in action

Implements #1699 .

Make it so that we preserve the tx method filtering setting when stepping between blocks.

Also fix some smaller issues and do some cleanup under the hood.

Fixes #1743
Fixes #1779

(I suggest review commit by commit.)

• Also show validator account balance on - closes #1811
• Fix address display (ie. tooltip) in the title line
• Fix address display in the details - enable address highlighting
• Use actual link for the address in the validator details table
• Provide a link to the account page (somehere ... maybe in the title?)
• Validator dashboard: Balance Distribution -> Escrow Distribution

Changes:

Balance displayed on the validator page

Address link in the title

Before

• Link points to this same validator page.
• There is the gray tick before the address

After

• Link points to account page
• No gray tick, since there is no identity mentioned here

Address displayed in details

Before

• Doesn't participates in address highlighting

After

• Participates in address highlighting

Also apply the highlighting feature introduced in #1776 to validator links.

This depends on #1813.

I suggest reviewing commit by commit.

Fixes #1821

Solves #1744

When showing validator links with names, we need to indicate the source of the those names, just like we do with other names coming from a registry.

Before:

After:

Add filter pills/buttons to tokens list

Closes #1770
Sync with oasisprotocol/nexus#914

note:

• can be tested by looking at network requests as Nexus changes were not deployed yet
• not adding Check MUI icon from Figma to a selected pill to avoid changing buttons width (poor UX)

There are some network / layer configurations that (if configured in the .env) result in not showing the graph on the landing page, but instead immediately redirecting to the dashboard of a Runtime.

This change makes it so that if we change to a layer using the layer selector, that layer is preserved, and next time we redirect from the landing page, we go to this layer.

This was a feature request for the Pontus-X browser.

This implementation depends on:

• #1793.

(Hint for testing: uncomment REACT_APP_FIXED_LAYER in .env, or see this live in action on the pontus-x branch: https://pr-1355.oasis-explorer.pages.dev/)

Fixes #1822.

Before:

After:

Extracted from #1777 and #1781

We are not handling new ROFL event (dev crash / prod warning)

Extracted from #1777

• need custom label in header
• currently header is misaligned compared to content cell due to Button width and padding

Created by https://github.com/oasisprotocol/explorer/blob/master/.github/workflows/generate-openapi.yml

If CI actions and checks don't run in this PR: close it and reopen.
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#triggering-further-workflow-runs

Fixes extra white space on mobile by removing an unnecessary empty in the "From" address field of the Transaction table.

Before:

After:

Unifies #1716 and #1783

Fixes https://github.com/oasisprotocol/explorer/actions/runs/14038221239/job/39301496628

Some account names come from Oasis, some from deltaDAO.
This commit makes the difference clear in the tooltips.

Built on (depends on):

• #1795

Tooltip for Oasis identities:

Tooltip for pontus-x (deltaDAO) identities:

Tooltip for self-acclaimed names (not changed):

Transaction Storybook is broken due to:

• LocalSettings PR

Error: [useLocalSettings] Component not wrapped within a Provider
    at useLocalSettings

• guard against incorrectly indexed tx not working anymore

TypeError: Cannot read properties of undefined (reading 'toLocaleString')

#1820 (comment)
Should we keep RAK on mobile?

preview (at the bottom)
https://pr-1838.oasis-explorer.pages.dev/testnet/sapphire/tx/e1b96d2135b6b2bc2b13a46aa37db7bc0ac23803bd04ed407c271a0c30a0d0c1

On Pontus-X runtimes, we need to look for named accounts in two sources:

• The named address repository at Oasis Nexus
• The named address repository at deltaDAO

This commit re-enables the first source, which was somehow lost along the way. (The second source was always working properly. that's why we didn't notice earlier.)

Example for tx 0x12f2161e312ae060ab97a907a3a18e079712511e58b6320e7f374b42da84da92

Before:

After:

Fixes #1844

https://explorer.dev.oasis.io/mainnet/sapphire/tx/0xc78d5387868fd4f1991a35a39eff51366e2ba45e38c563c5c3f6724ba378d7a6

Before	After

The settings on the test faucet links have been updated, so this should be OK again.

(This reverts #1807)

When showing token smart contract addresses, usually we are replacing it with the name of the token.

That is all good in transactions, but we should not do this in the title on the token dashboard page, when we explicitly want to see the address. (Showing the name would be redundant.)

Before

After

There is a regression in our CI tests.
When testing the availability of faucet.testnet.oasis.io, we hit a problem because of an interactive challenge which had to be recently activated because of attacks.

So we just skip that link, in order not to fail the test.

Closes #2150

Should be merged shortly after a new CLI release which includes oasisprotocol/cli#391.

Implements #1856.

Fixes #2167

Fixes #2047

Fixes #2163

Fixes #2176

New line should not be captured inside the env variable.

Followup to oasisprotocol/docs#1165

This PR:

• Adds boilerplate Foundry contracts that simulate Sapphire precompiles and decryption
• Implements Foundry tests
• Contains Rust FFI bindings
• Added Makefile with build, test, clean options
• Readme with instructions

Enables local testing of Sapphire-compatible contracts without using forks.

Enhancements to SiweAuth contract:

• Added statement and resources fields to the AuthToken structure
• Implemented functions to retrieve the statement and resources from an authentication token, and a helper function to decode and validate tokens

Test functions and cases:

• Added test functions to SiweAuthTests for retrieving statements and resources
• Updated test cases to verify the new functionality, including tests for statement verification, resource access

Description

Close #501. See related oasisprotocol/docs#1170 and preview.

Description

Close #507 and replace #519

TODO

• use ![code] snippets
• merge #534
• bump docs with latest sapphire-paratime changes oasisprotocol/docs#1167
• re-record video
• re-record video second try
• update video after approval (need to wait for Zach/Marketing to upload)

Description

#524 needs a separate bump in examples/ because Netlify doesn't include new changes.

I stumbled on this when deploying demo-rofl-chatbot contract on Testnet and as a test I set the initial domain to localhost. When I wanted to simply change it to playground.oasis.io, I realized it can't be done, because _domain is private in the super contract.

Preview

Description

Fix older style comment sapphire-dev to sapphire-localnet. Fix spelling.

This PR:

• Adds soldeer token folder in publish.yaml
• Removes integrations/Foundry folder from js-docs loop.

Description

All the rebasing in #524 lost a change.

Description

Relates to oasisprotocol/docs#1070 and blocks oasisprotocol/docs#1172

Diagrams are here and here

TODO

1. Why does Mermaid cli create new wider SVGs? 🤔
My local generation was weird.

Prepare new release to test out the new ROFL market module.

make function comment match function name

Fixes: #912

This PR adds foundry subchapter to tools.

Description

Close #1070 and blocked by oasisprotocol/sapphire-paratime#538

Given that switching to Mermaid extension is also finicky with detecting dark mode, I'm continuing down the current path of overriding themeCSS through the usage of cli tool. It appears we do need to order the new media query at the end per specificity.

Reviewer should also review color choices.

Least pretty, this, this and better

TODO

• re-generate SVGs in CI
• merge oasisprotocol/sapphire-paratime#538
• bump sapphire-paratime

Reduces ROFL stake requirement for ROFL creation on Testnet from 10k to 100 TEST.

Description

Blocked by oasisprotocol/sapphire-paratime#536

Adds yarn projects command:

Available commands:
  add <url> [name]
    Import a new project living on url
    
  dump [-o output_file]
    Dump all projects to JSON format
    Default output is 'projects.json'
    Use -o flag to specify a different output file

Currently supported importers are:

• GitHub
• DoraHacks
• EthGlobal

Adds https://github.com/oasisprotocol/demo-rofl-chatbot

Description

Do the todo. We currently test just with MetaMask, but I expect same helpers would work with Coinbase.

Fixes claiming reward event typo.

• cancel retry on account change

Closes #5

• adjust height, due to notification height
• fix mobile button size

Closes #6

Resources

Desktop	Mobile

• remove ts-ignore

The runtime history should be built on top of the roothash service, using observed blocks for block reindexing and round syncing. The roothash service should broadcast blocks as soon as they are finalized in consensus, whereas the block history should broadcast blocks only after they have been reindexed or synced.

Now, we have 3 ways to observe runtime blocks:

1. Method consensus.RootHash().WatchBlocks returns blocks immediately once they are finalized in the consensus.
2. Method rt.History().WatchCommittedBlocks returns blocks immediately once they are committed to local storage.
3. Method rt.History().WatchBlocks returns blocks immediately once they are committed and synced to local storage.

Comparing methods to previous solution:

• Previous 1 == Current 2

Moving key manager backend from ServicesBackend to ClientBackend.

I also refactored clients, trying to follow these guidelines:

• First define struct, then implement constructor, and finally implement all methods.
• Accept interfaces, return structs.

I think our light client service implementation is not very useful and that the whole service can be removed:

• The CometBFT light client is never used.
• The trust store is never pruned.
• The trust store contains only a few valid light blocks (one per epoch, not older than trust period).
  • This causes issues for the CometBFT light client, as it will give up if the primary provider cannot find light block at the requested height.
• Light blocks provided by the service from remote peers are useful only if they cannot be found locally.
  • This means, that the local consensus state must be pruned very frequently, i.e., faster than the trust period. I'm not sure if we want to have these kind of settings in production.

Maybe I overlooked something. What am I missing?

Closes #6070

RoundResults are now on-chain so there is no need to reindex them anymore. See thread for more context.

Related to #5738, I have confirmed this increases our history reindex ~30%, which is in line with what existing benchmarks predict.

Fixes #5903

Show block history indexer status, also closes #5998.

Rendexing:

      "indexer": {
        "status": "reindexing",
        "last_round": 3951368,
        "reindex_status": {
          "batch_size": 1000,
          "last_height": 18764680,
          "start_height": 18705681,
          "end_height": 25804727,
          "eta": "2025-03-28T19:30:00+01:00"
        }
      },

Indexing"

      "indexer": {
        "status": "indexing",
        "last_round": xxxxxxx,
      },

The consensus light client is currently used only for consensus state synchronization. However, in the future, stateless clients will also rely on it. Therefore, we have moved the trust root configuration to a dedicated section.

I was going through the development environment setup instructions again when setting up my new workstation and noticed that we use unnecessary quotes when setting up the Oasis environment variables (export OASIS_...="1") -- there is no need to use quotes there, since we're setting the variable to a single word.

The deranged deranged crate update has caused havoc in a lot of random crates due to overlapping PartialOrd trait implementations.

See jhpratt/deranged#18 and jhpratt/deranged#19.

Currently uses a fix from the fortanix/rust-sgx#726 branch which should be changed to a released version once it becomes available.