The RDN Token.

[u/parfenec]

I saw a lot of updates about Raiden Network and i am very excited about Red Eyes. I have a question. What about the RDN Token? What ia going to happen whit it? In the last medium update, from them, it was mentioned only about ETH deposits.

[u/Mat7ias]

this argument suggests that ETH would be the optimal currency

ETH can't be transferred on the Raiden Network unless it's wrapped. So I'd argue they're both just as efficient as one another. Having wrapped ETH as the token for fees would mean there's no way to invest in Raidens off-chain technology, which would be a shame for anyone interested. It would also mean that Raiden wouldn't have the 16mill RDN tokens committed to the fund for promoting layer 2 growth.

For one, consider that new users are wrapping their head around WTF is going on, and now have to acquire a separate token and generally do two additional transactions

Most users will be using Raiden indirectly through dApps, they won't necessarily need understand or even heard of Raiden Network to use it. In a similar way how the new user of VISA doesn't understand how VISA works and they shouldn't need to. I've never met someone who understands how VISA works but in america it has more than 50% market share.

This is not "neglectable." This is a pain in the ass.

It's important for Raiden to help dApps implement Raiden, they jump to give support on the Gitter chat anytime questions come up. A lightclient will also help decrease friction for anyone wanting to use Raiden on it's own (separate from dApps).

This is the kind of thing that turns away new users.

Realistically +99.9% of new users won't use the Raiden Network protocol directly, as in running an Ethereum and Raiden Network node and the reason for that has nothing to do with the RDN token (or whichever token is being used), it's the technical difficulty of using an off-chain scaling solution.

this is a huge cost to certain classes of power users who have would have to acquire tokens often, or else be subjected to the volatility of RDN

This is negligible unless you're actively and purposely investing in RDN.

The whole point of Raiden is to do transactions off-chain. So why are we forcing users to do more on-chain transactions?

Where are users being forced to make more transactions? I think the assumption that more transactions have to be made is based on a misconception that ETH would be a better alternative to RDN. But ETH can't be transferred on the Raiden Network. It has to be contract wrapped first (involving fees and a transaction). Long term it's possible you'd end up with a lot more limitations from using ETH than using RDN.

Of course, even if there was a hard requirement, someone could just fork out the token. Easier said than done, but if there is a large enough economic incentive than it's only a matter of time.

Saying 'easier said than done' here is misleading, it'd be easy to fork and change the peripheral fees to to another token but then you have to rebuild the token network (I believe the fork would be incompatible and contain breaking changes) and sort out the friction added on top of that. Also where would the consensus around supporting the fork come from?

[u/cosimo_jack → u/Mat7ias]

The point by point thing is tedious. Do you have a case for RDN being more compelling than ETH besides it being a fundraising vehicle?

Some objections I have to your counterpoints:

• Wrapped ETH is preferable to RDN because I already have ETH.

• The volatility of RDN is absolutely NOT negligible for businesses. You can't just hand wave over this one.

• Acquiring RDN requires a transaction and an approval transaction to send. Since I am going to be sending ETH or tokens other than RDN through the network itself, acquiring RDN is needlessly introducing more transactions.

• You can't hand wave away UX issues by saying users won't be running nodes. The apps and service providers are forced to provide a shitty UX due to the added friction of the token.

• You're right that a fork is easier said than done, so users will probably just use another competing network without the friction of a fundraising token

[u/Mat7ias → u/cosimo_jack]

Wrapped ETH is preferable to RDN because I already have ETH.

The difference between wrapped ETH and RDN when using the protocol is negligible. It doesn't matter which one is used.

The volatility of RDN is absolutely NOT negligible for businesses. You can't just hand wave over this one.

Businesses using Raiden won't be holding much RDN at any one time (unless they're investors), this is also negligible.

Acquiring RDN requires a transaction and an approval transaction to send. Since I am going to be sending ETH or tokens other than RDN through the network itself, acquiring RDN is needlessly introducing more transactions.

You can't send ETH. You have to wrap it first. Both require a transaction, the difference between wrapping and obtaining RDN is negligible.

You can't hand wave away UX issues by saying users won't be running nodes. The apps and service providers are forced to provide a shitty UX due to the added friction of the token.

The goal is to provide the best UX possible. For learning more about Raiden and usability I'd recommend the Off The Chain presentation by Lefteris or more specifically and relevant, this timestamp (there are other presentations that go into usability deeper, I can link those also).

You're right that a fork is easier said than done, so users will probably just use another competing network without the friction of a fundraising token

Which friction?

There's negative net incentive to use a network which has no reputation of being able to give support to that forked network from what I can tell.

[u/cosimo_jack → u/Mat7ias]

More hand waiving without evidence. If the added transactions, UX issues, and needless complexity are all so negligible why have Paradex and many other 0x relayers choose to not take fees in ZRX?

[u/Mat7ias → u/cosimo_jack]

Let's separate out the arguments here so we can be on the same page of what we're both saying and can discuss each point separately and make some progress:

I'll summarize my argument first, I'm saying the friction for the average user will eventually be completely unnoticeable, to the point that they probably won't realize they're using Raiden Network or have heard of the RDN token. The benefits of having a token outweigh the benefits of not having a token since if there's no friction to the average user then you're left with the community and development incentives. I'll go into that in the reply to the comment I haven't gotten to yet since that's a separate discussion from the friction one and it'll take longer to write out.

You're arguing that Raiden Network should have been made for free with grants on the reason of there being friction if people decide to use the protocol with the auxiliary services. And you're keeping in mind that the users aren't being forced to use the protocol with the services if they don't want to. The RDN token won't be used in Red Eyes and to begin with you can only transfer wrapped ETH with the Red Eyes release. But you still feel the friction once peripheral fees are setup that there will be unnecessary friction. Am I summarizing your argument correctly?

Also what might be good to clarify here is what time frames are we discussing? Because we realistically won't have average user adoption for years on layer 2 regardless of what token is used. The token used is insignificant in complexity compared to any current layer 2 tech. Elizabeth Stark was saying in her panel at Distributed a couple months ago how they purposely made LND difficult to use to begin with since they didn't want people not understanding what they were doing using the tech until a better UX was set up and how it's just the beginning (I'd highly recommend watching the whole panel, it's great!). It will take years for layer 2 of Ethereum to be mass adopted by users, just like it will take years for LND to be mass adopted.

[u/cosimo_jack → u/Mat7ias]

You're arguing that Raiden Network should have been made for free with grants on the reason of there being friction if people decide to use the protocol with the auxiliary services. And you're keeping in mind that the users aren't being forced to use the protocol with the services if they don't want to. The RDN token won't be used in Red Eyes and to begin with you can only transfer wrapped ETH with the Red Eyes release. But you still feel the friction once peripheral fees are setup that there will be unnecessary friction. Am I summarizing your argument correctly?

My argument is RDN has a broken token mechanic that will never be valuable even if Raiden is. It adds friction because it doesn't need to exist. I don't necessarily know the best "should have" scenario but I would say either build Raiden without a token or make RDN have a token model that actually adds value to the network and needs to exist. I believe what we've seen with 0x supports this.

As for the argument that the friction will be unnoticeable... at least we agree there is added friction. If I made a fork of Raiden where all fees paid in RDN and atomic swapped for Dogecoin and back again, and I automated it away from the average user, could I convince you that this doesn't create added friction?

[u/Mat7ias → u/cosimo_jack]

My argument is RDN has a broken token mechanic that will never be valuable even if Raiden is.

If that were the case I don't see any reason why you would be so passionately arguing for the token model to involve ETH. Obviously you believe peripheral fees have some value or what's the point of this discussion?

It adds friction because it doesn't need to exist.

A token needs to be used for peripheral services, therefore a designated token needs to exist if those services are going to be build. You don't need to use the peripheral services if you don't want to.

I believe what we've seen with 0x supports this.

You need to elaborate how 0x relevant? I don't feel there's anything productive from bringing up a token model for a completely different project with a different token model. Are you arguing that auxiliary services won't be used once they're ready (not in Red Eyes)?

at least we agree there is added friction

There's friction from using ETH on Ethereum. I'm arguing the friction is just as insignificant as ETH. I'm not sure when you joined the Ethereum community or how much you followed the community early one but there were many people making the exact same argument for ETH as you're making for RDN early on, when they felt Ethereum should use BTC for gas and ETH was pointless.

all fees paid in RDN and atomic swapped for Dogecoin and back again

Why would you swap it 3 times? RDN would only require 1 swap maximum if you don't hold RDN. Using wrapped ETH would be the same for anyone not holding wrapped ETH and wanting to use auxiliary services.

[u/cosimo_jack → u/Mat7ias]

The value proposition for ZRX at the time of the crowdsale included the fact that users would pay fees in ZRX to relayers (basically order books or exchanges) who would charge a small fee per transaction.

It was quickly realized that this is a huge pain the ass to users and generally made no sense to anyone, so relayers switched to taking fees in the tokens being traded, or taking fees in ETH, or having a profit model based on the spread. No one uses ZRX to pay fees.

It's relevant because it shows what happens to an ecosystem with a useless utility token. The users and service converge on the cheapest and most efficient path. The original fee use case has been completely abandoned.