Daisugi is an Ethereum-compatible test network for experimenting with post-quantum signatures. It brings together a network explorer, a test ETH faucet and account-abstraction infrastructure.

Use the Explorer to follow network activity and inspect what is included in each transaction. Test ETH has no monetary value.

Daisugi lets you test SPHINCS-like hash-based signatures, part of an ongoing effort by the Ethereum community to prepare for leanSPHINCS. The network will soon support an experimental version of signature aggregation, which makes it a testing environment for Ethereum's post-quantum migration.

NiceTry is an account abstraction (AA) wallet that supports the Daisugi testnet. Post-quantum transactions require AA, which many major wallets support only partially or not at all. NiceTry comes ready to use and connects directly to Daisugi's testnet and explorer. Any ERC-4337-compatible wallet will also work for testing.

To install NiceTry:

1. Go to the official NiceTry website ↗ and follow the wallet installation instructions for a supported browser.
2. Open the extension and create your wallet through the setup flow.
3. Copy your account address and request test ETH from the Faucet.

Account setup and transaction signing happen in the NiceTry extension. This portal does not connect to wallets.

View Daisugi connection details →

Select Daisugi in your wallet or configure the network with the following details.

Network name

Daisugi Testnet

Chain ID

1337

Currency

ETH (test ETH)

RPC endpoint

https://daisugi.fyi/rpc

EntryPoint

0x433709009B8330FDa32311DF1C2AFA402eD8D009

Bundler

https://daisugi.fyi/bundler

Open the Faucet, paste a valid recipient address and submit your request.

Each request sends 1 test ETH on Daisugi, with a 60-second cooldown per address. Open the returned transaction hash in the Explorer to check its result. A balance on another network is separate from your Daisugi balance.

Set up NiceTry, select Daisugi and fund your account with test ETH. Submit a transaction from the wallet, then search its transaction hash or UserOperation hash in the Explorer.

For account-abstraction operations, check both the UserOperation result and the enclosing transaction. A transaction can be included even when an individual operation reports a failure.