Intro
License:
Kusama Shield is developed under the MIT license.
Recommended wallet:
All current features have been tested with Talisman
Code repositories:
https://codeberg.org/KusamaShield/
- ZKSOLgen
ZK solidity verifier generator. - Interface
Kusama Shield React interface. - Solidity helpers
Solidity contracts and EVM helper scripts. - no-std Halo2 for Polkavm
Test instance:
https://kusamashield.laissez-faire.trade
How does Kusama Shield work?
Kusama Shield is a zk-powerd multi-asset shielded pool, allowing anyone to deposit any supported token into the shielded pool
User journey
- User generates a deposit transaction, generating a secret, the secrets gets wrapped in Zero Knowledge and takes a small piece of that data as a deposit token.
- Anyone that wants to withdraw the tokens, will connect their browser wallet to
How anonymous is the system?
The privacy score can be measured by the K-anonymity score. Which roughly translates to the more users that deposit and withdraws at the same time, the higher anonymity the systems gets, the goal is to get lost in the crowd and provide a
How does it compare to Monero?
Monero relies on decoy transactions
. To calculate the anonymity score of your Monero transaction we need to look at a block explorer, and calculate
\( k = \frac{\text{Total number of decoys in the block}}{\text{Total number of transactions in the block}} \)
Supported assets
Kusama Shield supports all ethereum erc20 asset as well as the native token on the chain where it is deployed.
Supported Networks
- Westend Assethub
- Moonbase
- Paseo Contracts Chain
Kusama Shield is compatible with any EVM chain that supports smart contracts in solidity and have an Ethereum RPC.
Westend Assethub
Note: Westend Assethub is currently bricked, use the Paseo chain instead
Faucet:
https://faucet.polkadot.io/westend?parachain=1000
Block explorer:
https://blockscout-asset-hub.parity-chains-scw.parity.io
Moonbase Testnet
Paseo Contracts Assethub
Ethereum RPC:
The current RPC is hosted by parity:
https://testnet-passet-hub-eth-rpc.polkadot.io
However due to strict traffic filtering we recommend that you use this RPC instance:
http://eth-pas-hub.laissez-faire.trade:8545
Add network to talisman:
Run your own RPC instance:
git clone https://github.com/paritytech/polkadot-sdk
cd polkadot-sdk/
cargo build --release -p pallet-revive-eth-rpc
RUST_LOG=info,eth-rpc=debug ./target/release/eth-rpc --dev --rpc-external --rpc-message-buffer-capacity-per-connection 1152048 --rpc-cors all -lerror,runtime::revive::strace=trace,runtime::revive=info --node-rpc-url wss://testnet-passet-hub.polkadot.io
Faucet:
https://faucet.polkadot.io/?parachain=1111
Native Asset:
PAS
Ethereum Chain id:
420420422
Paseo Paraid:
1111
Block explorer:
https://blockscout-passet-hub.parity-testnet.parity.io/
Kusama Shield Paseo demo:
Deploy Kusama Shield Locally
XCM Transfers
Send token transfers to and from other chains using XCM.
Kusama Shield is deployed on Paseo Hub chain
Supported Chains:
- Paseo Relay
- Paseo Assethub
- Paseo Hub
- Paseo Hydration
- Paseo Pop
Bridge:
1: Connect wallet
Connect your browser wallet and select a substrate/polkadot address.
2: Select to and from chain
Make sure you have funds on your account, use the faucet if needed:
faucet.polkadot.io
3: Press bridge
Tested xcm asset sending routes:
Paseo Relay:
- Relay > Assethub
- Relay > Paseo hub
-
Relay > Paseo Hydration
Unstable route, do not use -
Relay > Paseo Pop
Unstable XCM channel
Paseo Assethub:
- Assethub > Relay
-
Assethub > Paseo hub
No XCM channel open right now. See more here - Assethub > Hydration
-
Assethub > Paseo Pop
Polkadot.js Apps Chain link
Paseo Hub:
- Hub > Relay
- Hub > Assethub No supported channel.
-
Hub > Hydration
No open supported XCM channel. -
Hub > Paseo Pop
No open supported XCM channel. Polkadot.js App Chain link
Cross Chain Transfers
Kusama Shield may integrate with a defi protocol, allowing anyone to bridge and swap tokens on other ecosystems such as USDT(trc20), Solana, Zcash, XMR, ARB, SUI, etc to swap the native token to DOT with a low(0.5%) fee.
Integrate Kusama Shield
Operator guide
Host Kusama Shield UI instances
Best pratice:
- Own your own hardware
- Always respond to abuse requests with a link to the terms of service, ideally within 24hours
- Keep your systems up to date and happy.
- use ssh public key authentication
- Put Kusama Shield react app behind a proxy
- Always keep a good social relationship with your ISP.
Use your own hardware:
Buying a used server on ebay and asking your local data center or a datacenter nearby for a one unit rack slot, is a great and cost effective way to actually own your own hardware and have more control. Colocation costs are different depending on where(you can also ship your server somewhere cheaper) but for a single unit server your looking at 30-80Euro's a month for the European market. The most price effective way to is often to ask local datacenters or maybe you nknow someone working for a company that has server racks?.
Host using a VPS:
Select a VPS provider, ideally one from Tor's recommended providers | Good Bad ISPs.