Fixes #2213

Makes #2175 less scary

When I was testing #2215 I grabbed random test account addr from CLI and ended up with Couldn't load transactions. Unknown error: Cannot read properties of undefined (reading 'to')

https://pr-2216.oasis-wallet.pages.dev/account/oasis1qzgc7dvlls36q47z5y6dvu6ylaa78rkrduqtxgdr
vs https://wallet.oasis.io/account/oasis1qzgc7dvlls36q47z5y6dvu6ylaa78rkrduqtxgdr

As we are not filtering txs in Wallet and fetch all layers we may hit edge case:

• encrypted tx (with envelope)
• any other tx with missing body

Fixes: #648

See examples for added commands.

Closes #558

Considerations:

#637 (comment)

How to test

Run

./oasis state-sync trust  --network testnet|mainnet

end ensure you are able to do state sync with returned parameters.

In most other Go projects we have already updated. So now we can use the same golangci-lint version as eleswhere.

Fixes: #628

This now works:
oasis rofl machine logs --deployment testnet | grep "res"

Fixes: #592

This change refactors the squashfs build to produce bit-for-bit identical outputs across multiple environments, but the resulting images differ from those built with previous versions. We should probably do a major bump of CLI to 0.17 once this is merged.

I have tested this change on:

• Ubuntu host
• Ubuntu Docker container on Ubuntu host
• Debian Bookworm Docker container on Ubuntu host
• Ubuntu Docker container on macOS host

In all cases, the resulting rofl app builds produced identical Enclave IDs.

I wasn't able to avoid fakeroot: even with adding -all-root -force-uid 0, -force-gid 0 to sqfstar.
Also, I wasn't able to get it working without tar -> sqfstar.
I also added a warning to check for version version 4.5, because using 4.7.4 i get a different Enclave IDs.

Edit:

• Maybe it would be worth finding out where the difference between 4.5 and 4.7.4 comes from, because based on the changelog, it's not apparent to me. Then we could achieve even greater reproducibility. Will try a bit, but don't want to spend too much time on this.
  • 4.6.x and 4.7.x produce identical images, while 4.5.x produces different. So the change is in 4.6 .

I have confirmed the difference comes from the following bug fix in 4.6:

8.4 Sqfstar would incorrectly strip pathname components in PAX header linkpath if symbolic.

Will try switching from "--format=pax to "--format=gnu in the tar command.

This fixed the issue 🎉 This is now also reproducable across squashfs-tools >= 4.5

Closes #589 and closes #590.

If artifacts.builder is set in rofl.yaml, the given Docker image is now pulled at the start of the rofl build process and the progress of the Docker layer pulling is also shown in real-time, so the user knows what is going on.

Example output with artifacts.builder set to ghcr.io/oasisprotocol/rofl-dev:main-minimal:

Deployment: test
Network:    testnet
ParaTime:   sapphire
Debug:      false
App ID:     rofl1qp55evqls4qg6cjw5fnlv4al9ptc0fsakvxvd9uw
Name:       demo-rofl
Version:    0.2.0
TEE:        tdx
Kind:       container

Initializing build environment...
Unable to find image 'ghcr.io/oasisprotocol/rofl-dev:main-minimal' locally
main-minimal: Pulling from oasisprotocol/rofl-dev
1adabd6b0d6b: Pull complete 
98807ed13a7f: Pull complete 
e9511b254cfc: Pull complete 
Digest: sha256:2a93fa747fa5e2735d6fbdbbd1179dc077ebfcbb14df2694513c1cce96cb06c2
Status: Downloaded newer image for ghcr.io/oasisprotocol/rofl-dev:main-minimal
Building a container-based TDX ROFL application...
[...]

Found out while doing: oasisprotocol/oasis-sdk#2402

Also confirmed this still works for ROFL apps that don't use the build env.

Part of oasisprotocol/docs#1456

Merge after oasisprotocol/docs#1456

This makes it possible to execute oasis wallet create without any arguments, and get a wallet called test_wallet.

The goal of this change is to get our CLI tool more inline with expectations (hallucinations) of AI coding tools, in order to decrease friction for new developers.

Tested the new release in https://github.com/oasisprotocol/rofl-x402-service & https://github.com/ptrus/verisage.xyz

The TLS ceritifcate persistance is now fixed (oasisprotocol/oasis-sdk#2387)

Udpates and fixes from: oasisprotocol/oasis-sdk#2393

Fixes https://github.com/oasisprotocol/docs/actions/runs/19626086942/job/56195086882?pr=1574.

(I originally copied the pattern from the sub-chapters, but in case of the heading no anchor will be created).

Fixes: #1188

Fixes: #1190

Fixes: #1207

Fixes

{"args":["sapphire","oasis1qpn09fsupnx720uv6zav8vzgkcl3mgfkas7wpth2","oasis1qpn83e8hm3gdhvpfv66xj3qsetkj3ulmkugmmxn3","-13398826426497"],"caller":"client.go:155","db":"nexusmainnet","err":"ERROR: value for domain uint_numeric violates check constraint \"uint_numeric_check\" (SQLSTATE 23514)","level":"error","module":"postgres","msg":"Query","pid":730080,"sql":"\n    INSERT INTO chain.runtime_accounts_delegations AS old (runtime, delegator, delegatee, shares)\n      VALUES ($1, $2, $3, $4)\n    ON CONFLICT (runtime, delegator, delegatee) DO UPDATE\n      SET shares = old.shares + $4","time":"3.914196ms","ts":"2025-11-04T10:56:31.366742875Z"}
{"analyzer":"sapphire","caller":"block.go:493","err":"query 520 &{\n    INSERT INTO chain.runtime_accounts_delegations AS old (runtime, delegator, delegatee, shares)\n      VALUES ($1, $2, $3, $4)\n    ON CONFLICT (runtime, delegator, delegatee) DO UPDATE\n      SET shares = old.shares + $4 [sapphire oasis1qpn09fsupnx720uv6zav8vzgkcl3mgfkas7wpth2 oasis1qpn83e8hm3gdhvpfv66xj3qsetkj3ulmkugmmxn3 -13398826426497]}: ERROR: value for domain uint_numeric violates check constraint \"uint_numeric_check\" (SQLSTATE 23514)","height":11322402,"level":"error","mode":"slow-sync","module":"analysis_service","msg":"failed to process block","ts":"2025-11-04T10:56:31.367852125Z"}

tested the fix with the exact same query that fails on mainnet db (with rollback of-course)

Future TODO:

• update E2E regression test block ranges so that it covers at least one runtime undelegation

Fixes: #1180

Closes #2238.

Extracted PRs:

• #2313
• #2344
• #2345
• #2346

Part of #2307
Deps like @mui/material @emotion/styled @emotion/react are still needed, because of @mui/icons-material.

Closes #2239

Waits for:

• API deploy
• Design feedback

Sample acc:
https://pr-2288.oasis-explorer.pages.dev/mainnet/sapphire/address/0x705b2433b76c383C20AE0d60803334f0AD13b6e8

Sample acc without staking:
https://pr-2288.oasis-explorer.pages.dev/mainnet/sapphire/address/0xBa88f6A71763D01bc4DbcCefc8f3a92c1646e81B

Fixes #2146

Extracted from #2302
Preview from another branch https://pr-2302.oasis-explorer.pages.dev/

Convert remaining styled MUI as a part of MUI to shadcn migration.

Leaving out instances on the homepage as its getting removed in PR #2302 and replaced with new design.

Closes #2316

Part of #2146

Update remaining MUI typography to ui-library Typography component.

Removal of ConsensusTransactionDetails.tsx in TransactionDetailsElements.tsx -
cleanup after #1523

Instances of Typography - select variants left as homepage graph is getting removed in PR
#2302

Update the remaining MUI Button components to Oasis ui library.

Leaving out the instances related to homepage as they are getting removed in PR #2302 homepage redesign.

Closes #2306

Update all the remaining MUI links and styled links, to oasis library Link component.

Closes #2291

Before (mainnet, testnet):

After (mainnet, testnet):

Closes #2314

Extracted from #2302

Fixes #1858

Differences from design:

• Runtime accounts do not have a total balance right now - showing available balance.
• If available balance is zero but account has transactions I still show a link too, as user may be interested in account's history.
• Simpler tooltip / not repeating the same address

https://pr-2311.oasis-explorer.pages.dev/mainnet/sapphire/address/oasis1qz78ap0456g2rk7j6rmtvasc9v2kjhz2s58qgj90#root
https://pr-2311.oasis-explorer.pages.dev/mainnet/sapphire/address/0x5d6D0A8fF8355Eb766B8d9Cec37d8e4313166564#root

Before | After

Tooltips

Ignoring tooltip in tooltip weirdness:

cc @donouwens

Extracted from #2302
Waits for #2344
Peview from another branch https://pr-2302.oasis-explorer.pages.dev/

follows #2285 (comment)
#2302 removes other useTheme occurances and ThemeProvider can be removed after merging new homepage

• global search (desktop & mobile)
  https://pr-2343.oasis-explorer.pages.dev/search?q=ocean
  vs https://explorer.dev.oasis.io/search?q=ocean

• scoped mainnet search (desktop & mobile)
  https://pr-2343.oasis-explorer.pages.dev/mainnet/sapphire/search?q=ocean
  vs https://explorer.dev.oasis.io/mainnet/sapphire/search?q=ocean

• scoped testnet search (desktop & mobile)
  https://pr-2343.oasis-explorer.pages.dev/testnet/sapphire/search?q=ocean
  vs https://explorer.dev.oasis.io/testnet/sapphire/search?q=ocean

Partial implementation of #2317

Before:

After:

Part of #711

(regenerate commit: forgot to regenerate after appending a comment in 31168e4)

Extracted from #2302 as it is used everywhere not only in new homepage

https://pr-2313.oasis-explorer.pages.dev/mainnet/consensus

Update Info icon from MUI to lucide-react.

Example - Before:

After:

Revisits #2269
Part of #2244

Before | After

Before:

After:

Closes #2338

Fixes #2273

https://explorer.dev.oasis.io/mainnet/sapphire/address/0x3cAbbe76Ea8B4e7a2c0a69812CBe671800379eC8#root

Other use cases removed in #2302

used in:

• logo desktop/mobile
  https://pr-2341.oasis-explorer.pages.dev/mainnet/consensus
  vs https://explorer.dev.oasis.io/mainnet/consensus

• layer icons (layer picker/dropdown)
  https://pr-2341.oasis-explorer.pages.dev/mainnet/consensus
  vs https://explorer.dev.oasis.io/mainnet/consensus

(main select and mobile layer details/overlay)
https://pr-2341.oasis-explorer.pages.dev
vs https://explorer.dev.oasis.io

Migrate tooltips with more complex content

Needs oasisprotocol/ui-library#82

• Token row -> token icon with name / token origin
  https://pr-2299.oasis-explorer.pages.dev/mainnet/sapphire/token/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520
  vs https://explorer.dev.oasis.io/mainnet/sapphire/token/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520

• Metadata -> Repository URL help icon
  https://pr-2299.oasis-explorer.pages.dev/mainnet/sapphire/rofl/app/rofl1qpdzzm4h73gtes04xjn4whan84s3k33l5gx787l2
  vs https://explorer.dev.oasis.io/mainnet/sapphire/rofl/app/rofl1qpdzzm4h73gtes04xjn4whan84s3k33l5gx787l2

• Age column content
  https://pr-2299.oasis-explorer.pages.dev/mainnet/consensus
  vs https://explorer.dev.oasis.io/mainnet/consensus

regular tooltip (string content) but covered by tests

• rounded val (anywhere in app when we show token val)
  https://pr-2299.oasis-explorer.pages.dev/mainnet/consensus/address/oasis1qpg2xuz46g53737343r20yxeddhlvc2ldqsjh70p
  vs https://explorer.dev.oasis.io/mainnet/consensus/address/oasis1qpg2xuz46g53737343r20yxeddhlvc2ldqsjh70p

Slack request: link ROFL header in homepage to ROFL list

minor fixes found during tests

• homepage section headers are lg according to Figma (except Ecosystem)
• subpage main titles should be xl
• wrong i18next imports
• wrong validators total count in lists (total count is decreasing with every page currently https://explorer.oasis.io/mainnet/consensus/validators?page=2)

Fixes #2326

Will fix e2e tests in #2302 too

Tooltips with disable prop

Needs oasisprotocol/ui-library#84

• Consensus tx method icon (mobile enabled / desktop disabled)
  https://pr-2301.oasis-explorer.pages.dev/mainnet/consensus/tx?page=2
  vs https://explorer.dev.oasis.io/mainnet/consensus/tx?page=2

• truncated value with MaybeWithTooltip (truncated enabled / original value disabled)
  https://pr-2301.oasis-explorer.pages.dev/mainnet/consensus/tx/25ad10b1ca91abc5ec3d74fe20843015a52b33646dea299096ac0b3277324ea2
  vs https://explorer.dev.oasis.io/mainnet/consensus/tx/25ad10b1ca91abc5ec3d74fe20843015a52b33646dea299096ac0b3277324ea2

I did not found any issues except base fonts set by MUI (in other cases tailwind already took control over styling). In our case Oasis UI Lib system Inter is slightly diff than variable font rendering.
I guess we want to use variable fonts in UIL at some point, right?

Closes #2357

• we need to keep "View App" button to keep search consistent. I am not sure removing it everywhere is expected.
• keeping "ParaTime" line below app name. Scoped search return all networks for a given layer + global search return all networks for all layers. It is easy for users to get lost without this row.
• name copy to clipboard copies app id, right?

global search
https://pr-2358.oasis-explorer.pages.dev/search?q=demo-rofl

testnet scoped search (mainnet still avail at the bottom/collapsible section)
https://pr-2358.oasis-explorer.pages.dev/testnet/sapphire/search?q=demo-rofl

Changes include

• max content width added as on the other pages,
• sticky header,
• limit search input width on desktop
• added outline variant to devnet and testnet buttons in ecosystem cards

Design changes approved by @juresobocan
Closes #2359

Before:

After:

click transfers in details section to trigget scroll (table header and tabs should he visible)
https://pr-2324.oasis-explorer.pages.dev/mainnet/sapphire/token/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520
vs
https://explorer.dev.oasis.io/mainnet/sapphire/token/0x39d22B78A7651A76Ffbde2aaAB5FD92666Aca520

note: styles follows design guide and UI Lib. New Explorer designs use diff colors and font sizes for chart tooltips, but imo it's better to keep tooltip consistent across app.

any chart
https://pr-2340.oasis-explorer.pages.dev/mainnet/consensus
vs https://explorer.dev.oasis.io/mainnet/consensus

Don't break line on space
https://pr-2361.oasis-explorer.pages.dev/mainnet/sapphire/tx/0x9f28eefcf65f1cce4514d57c3d508d5da5227e59a60cee58ebb15e3f13adbabd

Related oasisprotocol/rose-app#307 (comment)

Fixes #2333

Accidental label change in #2192

https://pr-2304.oasis-explorer.pages.dev/mainnet/consensus/validators/oasis1qqtmpsavs44vz8868p008uwjulfq03pcjswslutz
vs https://explorer.oasis.io/mainnet/consensus/validators/oasis1qqtmpsavs44vz8868p008uwjulfq03pcjswslutz

from sync meeting. we want to include UIL Tooltip update in a next patch release

(Neby tooltip for example)
https://pr-2336.oasis-explorer.pages.dev/mainnet/sapphire/token
vs https://explorer.dev.oasis.io/mainnet/sapphire/token

This PR adds a TypeScript/Node.js client SDK for Oasis ROFL with support for key management, metadata operations, and transaction signing. Provides endpoints
for:

• Key generation: RAW_256, RAW_384, ED25519, SECP256K1 signature schemes
• Metadata operations: Get and set ROFL app metadata
• Transaction signing & submission: Sign and submit authenticated transactions with both standard and Ethereum-style support

Closes #2357

This PR adds support for /rofl/v1/tx/sign-submit to the python ROFL client.

This PR addresses 3 follow-up feedback from the initial rofl-client/ts sdk PR

1. add support for the recently added queries endpoint and use the types for the arguments and responses by @ptrus #2365 (comment)
2. update transaction handling by @rube-de #2365 (comment)
3. support ESM and target ES2022 by @rube-de #2365 (comment)

Bumping Oasis Core to 25.7.

Also upgrading CLI to 0.17.0 and Oasis Core to 25.7.x for the rofl-dev Docker image.

Fixes: #2369

TODO:

• test

This PR:

• adds get_app_id() helper for /rofl/v1/app/id
• rewrites documentation to sphinx-format for consistency with https://github.com/oasisprotocol/sapphire-paratime/tree/main/clients/py
• runs formatter

Flow before: push a next version tag and then merge bumped package.json.
Flow after: merge a bumped version in package.json and then push a tag.
This ensures tag can be on the correct commit and matches flows in other repos.

(if you tried to merge bumped package.json and tag it currently it would fail https://github.com/oasisprotocol/oasis-sdk/actions/runs/19141519782/job/54707605100 npm error Version not changed and require manual npm publishing)

Based on #2370

set_metadata returns an empty response

Does this fix #2375?

We observed certificates not persisting in some cases when the scheduler panicked soon after writing. Lets fsync to be sure.

Related #2365 (comment)

Uses https://docs.npmjs.com/trusted-publishers because auth tokens are becoming useless for CI https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/

Also includes id's from #2374

Please update the testnet policies @kostko when available

Proposing we add some more codeowners for rofl-client packages and typescript code.

Removing @pro-wh due to 😢

Unknown owner on line 2: make sure @pro-wh exists and has write access to the repository

It failed to release in https://github.com/oasisprotocol/oasis-sdk/actions/runs/19138314243/job/54696104648 because it picked the rofl-containers/v0.8.3 tag instead of the rofl-client/py/v0.1.6. The commit was tagged with both tags.

Building source distribution...
/home/runner/work/_temp/setup-uv-cache/builds-v0/.tmpOFUa79/lib/python3.12/site-packages/setuptools_scm/version.py:108: UserWarning: tag 'rofl-containers/v0.8.3' no version found
  warnings.warn(f"tag {tag!r} no version found")
Traceback (most recent call last):
  File "<string>", line 11, in <module>
  File "/home/runner/work/_temp/setup-uv-cache/builds-v0/.tmpOFUa79/lib/python3.12/site-packages/hatchling/build.py", line 34, in build_sdist
    return os.path.basename(next(builder.build(directory=sdist_directory, versions=['standard'])))
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

As a workaround, I tagged a different commit with rofl-client/py/v0.1.6. This fix should fix it for future releases.

Need it for: #2402

Alternative, we could recreate the file on update.

Depends on #634

Closes #500

This change replaces occurrences of interface{} with the predeclared identifier any, introduced in Go 1.18 as an alias for interface{}.

As noted in the Go 1.18 Release Notes:
This improves readability and aligns the codebase with modern Go conventions.

🔗 zboto Link

🔗 zboto Link

🔗 zboto Link

🔗 zboto Link

Closes oasisprotocol/oasis-sdk#2298

PREVIEW

This PR:

• Creates a new use case guide for key generation using appd REST
  • This guide goes through how to sign message on EVM chain. Base in this case
  • Generate key for Base via appd key REST API (secp…)
  • Send ETH(test) to ROFL key
  • (Deploy Contract via ROFL key)
  • Send ETH(test) back to user via RPC

The example repo can be found here: https://github.com/uniyalabhishek/demo-rofl-keygen

Based on #1527. This PR adds a Trustless AI agent guide.

Oasis Core 25.5 has brought support for stateless client nodes, which are particularly suitable for ROFL nodes.
We are documenting that here.

Implements fixes reported during DevConnect hackathon.

• Adjustment for mobile DocCards on homepage, reducing image and gradient size to be able to show more content on an average viewport of a phone. Closes

Before:

After:

• Align Use Cases and Build DocCards into one row on desktop
  Before:

Adds Build->Use cases as a separate doc card section on the landing page.

Fixes #1549

Fixes #1568

E.g. ctrl+f "sepolia" a few times on https://deploy-preview-1569--oasisprotocol-docs.netlify.app/build/use-cases/key-generation

Fixes #1284

https://docs.oasis.io/search/?q=rofl

Before	After

(e.g. second result came from

)

Followup to #1544

It turns out 5GB is not enough to download all images in compose + the system ones. 10 GB works fine.

Bumps the rofl-8004 image.

Since ROFL is already a tag and mentioned in the first paragraph it makes sense to trim "on ROFL" in "Cross-Chain Key Generation on ROFL (EVM / Base)" so that it fits one line.

arXiv version: https://arxiv.org/html/2412.02634v1
IEEE version: https://www.computer.org/csdl/proceedings-article/sp/2025/223600b437/26hiUjFXiP6

The IEEE version is not publicly accessible so we can't host it.

This PR updates the Oasis SDK diagram:

• adds ERC-8004 box
• adds Typescript and Rust bindings for ROFL client
• ROFL-powered apps are now showed as a server having a TEE padlock inside

Adds New Delhi buildathon ROFL projects:
sentibot https://app.akindo.io/communities/xKWknzrrWCmd2JpeP/products/4e9BlqL07Cm3WxX0
zk-oasis-sdk https://app.akindo.io/communities/q34EL31MBuj2NOon/products/eae8VRlZ0u7wJ93P
MinePlay https://app.akindo.io/communities/nPZgeVMqGU0JAkVA3/products/VwZazZWJ7c1erJj7
Shadeswap https://app.akindo.io/communities/Mzj3mmXVWcEde2WZ/products/gXAzBgdkAHde89Dm
PredaMark https://app.akindo.io/communities/peW1noEwpia44mzd/products/7m1zlZa1jfdmgz4mJ
Unipoll https://app.akindo.io/communities/63damjWkXSPgdmgE/products/3d7Xlan1jc9wVBw
SapphireX : Lending Protocol https://app.akindo.io/communities/X4ZGXPaz9TOVG4VB/products/93vVlGOmQsQvRE6o7

Task: #139

Fixes "Warning: Each child in a list should have a unique "key" prop." and fixes displayed duplicates inside filters:

Task: #141

This PR adds Taiwan RWA hackathon winning project submission.

This enables simple building with docker compose build.

Init work to resolve rename the Telegram API token variable from TOKEN to TELEGRAM_API_TOKEN oasisprotocol/rofl-app#231

2 GiB of memory and 10 GB of storage suffices.

Removes the local queue, which doesn’t support multiple transactions per sender. All incoming transactions are now added to the main queue.

Closes #6321

Motivation:

When enabling aggressive pruning node may fall behind. Whilst unlikely, the consequence may be the node breaking its commitment, which could results in lost rewards, possibly registering its availability when it is actually not ready, or worst case penalties (don't think this would happen actually).

Solution:

To prevent it, we should offer validators a maintenance command that should be called if pruning is enabled later on, before starting the node. This way freshly started node is guaranteed to be healthy.

As with compaction command, I have started with consensus databases only and suggest to add runtime databases for the follow-up. Moreover, I quickly tested that this command does not prune past the minimum reindexed height, in case of configured runtimes.

Automatically prune on the node startup?

For now this is not the case:

• Just pruning without compacting is not particularly useful. Unless we also automate compaction as part of the startup, the operator is forced to stop the node once the pruning finishes.
  • Bad ux, also possibly wait if the node already registered.
• I don't want to automatically enable forced compaction on the startup as this is inefficient assuming the operators restarts twice in a row, e.g. due to fixing config, possibly triggering corner case observed.
• Given this command is experimental and a bit hackish, I would prefer if we do not automate pruning on the node startup, at least for few months until we know if there is anything unexpected that could happen.

How to test:

Have a node with valid state, doesn't have to be synced. Configure pruning to retain less data and run:

oasis-node storage prune-experimental --config etc/config.yml

Following that trigger compaction:

oasis-node storage compact-experimental --config etc/config.yml

Ensure the node is able to sync correctly and that disk space has been correctly reclaimed. You can also configure a runtime and test this command does not prune past the min reindexed height.

Follow-up:

• oasisprotocol/docs#1469
• E2e test?

Closes #6352.

Considerations - #6355 (comment)

Removes dependency on common node's current block height.

Reverting slice changes from:

• #6383

Inspired by #6360 and replace all.

There is a new function added in the go1.21 standard library, which can make the code more concise and easy to read.

The goal is to make the storage worker less dependent on the common worker to make it easier to modify each independently.

Closes #6382

How to test:

Run stateless client node with at least one configured runtime (triggers history reindex).

Prior to this fix, if you set your trust root to be younger than your configured provider's last retained height, your indexer will get stuck. This PR should fix this.

These changes will also print REK in base64 form.

"rak": "0IoOQWOxbybG2G8jgDbpp4qvxVUi8bSMUtv5gGUr+q4=",
"rek": "AmNrJbyfkck+3cSdRCJR0jphY3yVI1LEzt+OkfHE2gg=",

There is a new function added in the go1.21 standard library, which can make the code more concise and easy to read.

Required to use nix::ioctl_readwrite.