tornadocash / tornado-relayer Goto Github PK

Any ideas why? Since all these supposedly missing are in the /src folder.

Mainnet Txn: https://etherscan.io/tx/0x4007f0f8fd09037465eb0bc4a31a2d2dfba69e9b3ba8d2e436c4679896595d25
Address: mainnet.serverless-relayer.eth

I haven't deployed testnet relayer because I don't think a testnet relayer is necessary and it's inconvenient to deploy another instance on a serverless platform. Please let me know if a testnet relayer is really really necessary.

I think this relayer has the best scaling ability.

Telegram: No username, find me in the group via 'Hertz'

Hello guys,
I have deployed the relayers below, apply for listing on UI, thanks

Mainnet

• ENS: mainnet-v2.goblin.eth
• URL: https://mainnet.polkadot.live
• Example transaction: https://etherscan.io/tx/0xa09cd896cdb9d44987cffebd3c32034dbe79d3f87026334604ecf44058b86a22

Goerli

• ENS: goerli-v2.goblin.eth
• URL: https://goerli.polkadot.live
• Example transaction: https://goerli.etherscan.io/tx/0x2dc159be54c4a1ead14f60f1a06d2b11b34445be72414108700833786c5288cb

Telegram: @tornado_dav

Mainnet
ENS: mainnet-v2.tornchina.eth
URL: https://mainnet.tornchina.com
Example transaction:
https://etherscan.io/tx/0x48356f95a738b28d324af6308b73bac0cde500a1039f93caf22b70d83462f0a5

Goerli
ENS: goerli-v2.tornchina.eth
URL: https://goerli.tornchina.com
Example transaction: https://goerli.etherscan.io/tx/0x8f63f7687b56e8b6f4fed103f592400d1b2865d89566380962a45f0148455505

I have a relayer which I would like included in the available relayers. Where do I publish the details?

Sorry duplicated

I go

yarn start

and get this error

Hi Tornado team and particularly @rstormsf !

I deployed a v4.0.0 relayer with a 0.02% withdrawal fee.

Hey team,

I'm hosting a relayer at tornado.mewwts.xyz, would love to be added to the list in the app for increased visibility.

ENS Record: v2.hertz-relayer.eth
Mainnet Txn: 0xa2567bb34f801b10caaf7ab45c66eb76f7479a79de2eaf02c54ecd74f23d6bd2

Telegram: No username, find me via Hertz in the group.

Hi guys, I just set up a new relayer on AWS.

Mainnet

• ENS: mainnet-v2.smillence.eth
• URL: https://mainnet-v2.smillence.xyz/
• Withdrawal transaction: https://etherscan.io/tx/0x7cf32808c2c7480dcbe7de2f2f771b3d45dd2c5d17a65221b029c996f10600b3

Goerli:

• ENS: goerli-v2.smillence.eth
• URL: https://goerli-v2.smillence.xyz/
• Withdrawal transaction: https://goerli.etherscan.io/tx/0xba571fc28ce0753ac0969910e232f06d5205f10e78d990ad890a9bef32a14285

Telegram: @Smillence

Telegram handle: @ninjavisa

goerli

• transaction: https://goerli.etherscan.io/tx/0xf618dc022d4ccf947806960adf0b88d907479bc9d08308a7e76ee328b2f13c49
• url: http://goerg7hhmkss3cvz.onion/

mainnet

• transaction: https://etherscan.io/tx/0x45f21a9484e0d1b2eb7b9c1e3ce79ed01e3b1e6e5241eb5eaea75518a18610c0
• url: http://mainwxpegvryfkva.onion/

Hey @rstormsf !
Just setup a new relayer, tested in both networks, uptime is controlled by me and funds are in place.

mainnet-v2.therelayer.eth - Transaction:
https://etherscan.io/tx/0x71d40bdf8c79164eb7c6d989139b0082c43aa73026aa155abc92bbdbfdc10ae1

goerli-v2.therelayer.eth - Transaction:
https://goerli.etherscan.io/tx/0xf25b1b227665bc4d73b6e040a8af13c257481039ae50695c6a40422c6d3757b6

Telegram ID: @mrdmc

Let me know if there is any other information needed.

goerli ens: goerli-v2.tsunamidev.eth
goerli withdrawal:
https://goerli.etherscan.io/tx/0x68a9a43b325569b30007c01756dc3a3a4e10ba0b81cf5627223a7a6d46f916bf

mainnet ens: mainnet-v2.tsunamidev.eth
mainnet withdrawal: https://etherscan.io/tx/0xac7baf593be0966c2ac6ccd122f1079018f3bc82a3e4d974dfb481d326ea96c6

Relayer status page: https://status.tsunami.to

telegram: @tsunamidev

Since Binanace Smart Chain relayers do exist now, can the codebase be updated to allow for running BSC relayer nodes?

I setup and tested the relay via cli and also website and everything seems to be functional.
It will be set to only 0.03% fee

kovan.cheap-relayer.eth
https://kovan.etherscan.io/tx/0xa6a7e3086c7e64882a481ab1b1a25cc774ac050116a2d925e5a9c34c82e9fafa

mainnet.cheap-relayer.eth
https://etherscan.io/tx/0xbf0e14d5b01c2877f3bd62cf9fb1d1324e818114e04f747d9b412d1ba8011ccd

Let me know if anything else is needed.

goerli-v2.tornadocomes.eth

https://goerli.etherscan.io/tx/0x67ee661abaebfe4ef8bb3f503b0cee7471c6ab7c2e7e313e6b8d0311ccd4ebc9

mainnet-v2.tornadocomes.eth

https://etherscan.io/tx/0x5a30ae09a2f219f670916d138c730d2e7fd7fff73af5ff320a30c15ee4dba2f0

url

tornadocomes.com

tg handle

@SilasYayoi

No matter how many times I try and which relayer I choose, still getting the above error.

During withdrawal, it goes to the very end where it shows "Accepted" then finally this error.

I also noticed that the "recent deposit" entry is not present for this deposit in the Tornado Deposit UI perhaps because i switched to ETH network while the deposit transaction was midway. Right now the funds are locked for me!

Any assistance will be appreciated! Thanks!

Note: After using wallet for gas payment, this problem went away

Hello, I have deployed a relayer and tried to withdraw from it with a MAX_GAS_PRICE set to 100 GWei, but it seemed not effective when withdrawn and took 267 GWei when sending a transaction from relayer.
transaction

Hi guys,
My relayer is now up if you want to check it out. I can add a second worker if needed. Fee currently at 0.045%.

Goerli:
goerli-v2.spoperalbi.eth
https://goerli.etherscan.io/tx/0x67562bbe064017d66deb6be87b8694663df60b1004aa4f539c8d65ec7d485bc0

Mainnet:
mainnet-v2.spoperalbi.eth
https://etherscan.io/tx/0xf2b51bc998170053e4e157e4c29c8ca6d0a6c589223238d7cd5e8b36339ac914

My Telegram @spoperalbi

In the README in the Deploy with docker-compose section point 1. I think that the probably file to be downloaded should be from the master branch now that the mining is merged into it.

And in Run locally point 6. it says to run the following command but the command is not specified.

mainnet.openbridge.eth
kovan.openbridge.eth

everything is running

goerli-v2.tornadosolutions.eth: https://goerli.etherscan.io/tx/0xf678b07dd9e82e68f0b82d65b12cd8c0bae7585045eb8f57c71a8a085b05476d

mainnet-v2.tornadosolutions.eth: https://etherscan.io/tx/0x1bc64457f2eb2e67c4dd175c56a33e2a7a8823ff75ebb9d2cd41bcecc1b314af

You can reach me on telegram: @positionidle

Goerli (goerli-v2.best-price.eth)
https://goerli.etherscan.io/tx/0x58fd444b9cfd10b4fd73cd1be8fd7a3821fd1edb1481f37379b77f28e0a93f8b

Mainnet (mainnet-v2.best-price.eth)
https://etherscan.io/tx/0xea6925f12a2395614b4cda67922f61de03744184fa7c8854ca49f931a9c9ba9a

Telegram: charlesyos

Goerli ENS: goerli-v2.degen-relayer.eth (transaction)
Mainnet ENS: mainnet-v2.degen-relayer.eth (transaction)

Telegram: @BlankerL

mainnet-v2.torn-relay.eth (mainnet.torn-relay.com)
https://etherscan.io/tx/0x136530f74cb0005ff7b500f057580ef8819bb0bfd0a1c35abb6d23c14ebbddbc

goerli-v2.torn-relay.eth (goerli.torn-relay.com)
https://goerli.etherscan.io/tx/0x142492b9689c3a54dae1f2b4abc301864df2645cee7983342b840a74bcf72d64

Telegram handle
@tornrelay

I setup and tested the relay via cli and website and everything seems to be functional.

kovan.gaasservices.eth
https://kovan.etherscan.io/tx/0x2e5104248e9ac16525c113becca7aeb6ae75743ed69b1e64fd61c22de8312f4e

mainnet.gaasservices.eth
https://etherscan.io/tx/0xa09c05dc4191042e2aad9337cd4705a8f36901c461f12d2e59b0bfda0675fd96

Let me know if anything else is needed.

Telegram : @Danhald

Hey, my telegram is Telegram: @pracandybox

Mainnet

• ENS: mainnet-v2.steamer.eth
• URL: https://mainnet.dfi.today
• Example transaction: https://etherscan.io/tx/0xbe62b011d09c4e9fa196499337b465cea0c72633421f51e278498883dd2f00f9

Goerli

• ENS: goerli-v2.steamer.eth
• URL: https://goerli.dfi.today
• Example transaction: https://goerli.etherscan.io/tx/0x2fc00abafc36d14a8a119effc3b3e485893ef1fb251238df950eb9020df0b092

Hey, I hope you can help me understand what I am doing wrong.

I set up a relayer (deployed with docker-compose) and everything is running and working (./status etc. all 'normal').

My ENS Domain mainnet.*.eth is pointing to my address mainnet..com
and kovan..eth to kovan.*.com and both to the ip of the server the relayer is running on.

Using my "kovan.*.eth" domain as custom relayer for the kovan version of tornado.cash works just fine, but if I want to test the "mainnet.*.eth" domain for the mainnet version I always get the "Can not fetch status from the relayer" message.

They are all setup the same way, so why is the kovan relayer working, but the mainnet one not?

Thanks in advance! :)

EDIT Solution was:
Have at least 0.15 ETH in your relayer address.

Hi guys, I deployed a new relayer.

Mainnet:

• ENS: mainnet-v2.defidevotee.eth
• URL: https://mainnet-v2.defidevotee.xyz
• Example transaction: https://etherscan.io/tx/0xf79039c315489c711d9fe9c3ff5186aba3499edcb1bd8ab8c26cc63df8f32573

Goerli:

• ENS: goerli-v2.defidevotee.eth
• URL: https://goerli-v2.defidevotee.xyz
• Example transaction: https://goerli.etherscan.io/tx/0xbd750915b7c5fd1b68849cd74a59580cd5e1ec796bd6ba9224a9b1acd4f6fd37

Telegram: @defisupporter

mainnet.lowcost.eth
kovan.lowcost.eth

everything is running (tested kovan & mainnet)

kovan - https://kovan.etherscan.io/tx/0xa94619f0543d1b0dd5316035c095817447b2ed9106365917b0be12cc8fc19460
mainnet - https://etherscan.io/tx/0x4684bc52672891cbbfaff4a13f95fc720894cbf01ba3af8727e26f5cb198f7eb

kovan.relaymy.eth
mainnet.relaymy.eth

Thanks!

I created a new relayer:

mainnet.releth.eth - Transaction: https://etherscan.io/tx/0x7a1cd7c938c32315082ecaeb471389e32d66fdfa74c7da015aede3c0a70111fb
kovan.releth.eth - Transaction: https://kovan.etherscan.io/tx/0x9037f540cf949d77210b837bc2bc7fe462c159900b36f1ee3c06e7e76715fc3e

Hope it is helpful.

I'm mainly asking for myself, but after searching the documentation I found no mention of this. Since you have to submit your "note" to a relayer in order for them to process it, wouldn't relayers be able to behave maliciously by recording all "notes" they process? Similar to a tor exit node recording all it's traffic, except in this case the relayer knows the source address as well!

Or am I mistaken on how the whole relayer process works? Is crypto magic used to hide the source address and the relayer can only see the destination address? I recommend documenting what's going on, and/or just answering my question here please :).

Do any 3rd parties (including tornado.cash webservers) see your "note" when a relayer is used, or is JS crytpo magic used to prevent that? Aside: It seems to me the compliance tool should only ever be run locally.

Hey guys,
if I understood your telegram messages correctly this the correct next step? Well I hopefully set up a relayer correctly and its working!

Registered these domains extra for this 😀:
mainnet.relayme.eth, kovan.relayme.eth

Do you only need the ENS domains? Or is there anything more you need from me? :)
Greetings

P.S. I just read about #7 - is this an issue if there arent this enough ETH (0.15) on the account?

For withdrawals through a relayer, the current implementation charges fees by the following scheme (notation mine, feel free to correct):

relayerFeeCurrent = noteSize * relayerFeeLevel + gasLimitPromised * gasPricePromised

To take a concrete example:

relayerFeeCurrent = 100 ETH * 1% + 500 000 gas * 20 gwei = 1.01 ETH

There are multiple problems with this scheme. The main one is that in practice the relayer's costs don't depend on the note size. Submitting a withdrawal for a 0.1 ETH and a 1000 ETH note is the same cost and effort for a relayer. The scheme thus results in rent-seeking behavior, which is economically non-optimal.

An economically optimal scheme would look like this:

relayerFeeOptimal = gasLimitPromised * gasPricePromised * ( 1 + relayerFeeLevel )

An example, with a different fee level:

relayerFeeOptimal = 500 000 gas * 20 gwei * ( 1 + 40% ) = 0.014 ETH

The actual fee level is not the important part, as it could be set to generate the same revenue for the relayer. The point is transparency. To get the same revenue (1.01 ETH) with this model, they would have to admit they are operating with a 10 000% (!) feeLevel when processing 100 ETH notes.

This new scheme reflects better the proportion of the actual fee, i.e. how expensive it is compared to the user withdrawing without a relayer, using their own ETH. That helps users make a rational decision between relayers (that is, if they know they have options, which is not really the case right now). Competition will drive fee levels down, making Tornado cheaper, attracting more users, and ultimately increasing the anonymity sets.

The above scheme doesn't deal with another problem, which I will address in another issue.

Edit: corrected equations and wording.

I'm trying to test a relayer as hidden service and I found few problems:

Those two line:

It should be more clear that if you want to run it as hidden service you do not need nginx and letsencrypt (and probably dockergen but I'm not sure of what it does).

Moreover the web UI should not enforce https for .onion's relayers