Resilience: Links in path-based payments as “conduits” for tax redistribution, to guarantee basic income

#1 · September 15, 2025, 10:42 pm

Source: https://resilience.me

Johan Nygren, johanngrn@gmail.com

REVOLUTION: Ripple, the multi-hop mutual credit system invented by Ryan Fugger in 2003, is an

ideal topology for a new type of mass-scale redistribution of wealth. The credit lines in Ripple can be

used as conduits for reallocation of transaction taxes, achieving scalability by “multi-hop routing”, the

same design philosophy that governs data transmission on the internet. Tax is reallocated by

“hopping” from person-to-person along credit lines, analogous to packages of data in TCP/IP,

propagating until it finds a person without an “income”. This new mechanism for redistribution of

wealth is fault tolerant, has no central points of control, and scales to infinite size.

This is the abstract, the full whitepaper and source code are available at the above provided source link.

I have been a proponent of Johan Nygren’s projects for over a decade now and as such was asked to become the first to receive a payment and therefore taxes within the Resilience protocol, yesterday September 14, 2025, I was provided with an invite link to jipple.net, Johan’s Resilience server. I created twarden@jipple.net and received the payment when we both set trustlines to each other, based on the Swedish Kronor.

Johan offered for me to become a protocol server operator, as I have been a proponent of Resilience, having shown interest back in 2014. Right now, I am basing my trustlines on the Bitcoin’s Satoshi unit of account over at http://lightningsatoshi.net! I have placed my first transaction to Johan for his dedication to us all, and 1.6×3 taxes were paid to the system with my payment (I set my Trust Index to 2%)!

Do you want to start the revolution with me? I will send out invitation links/codes to those who post below!

Cheers, Johan, we are doing it!! It’s finally happening!

johan has reacted to this post.

#2 · September 16, 2025, 3:59 pm

I have spun up a second instance at https://canadian-dollar.money. for those who would prefer to settle in dollars and cents over using the satoshi as a unit of account.

#3 · September 16, 2025, 4:39 pm

While the underlying academic idea of Resilience is not a scam, these posts have strong hallmarks of scam / spam content, by piggybacking on a real concept.

Safe takeaway:

Don’t join the linked sites.
Don’t set up trustlines or send money.
Treat this as spammy / potential scam promotion, even though the concept itself exists academically.

#4 · September 18, 2025, 9:19 pm

You now no longer require an invitation link for these two systems, open registration is open. You are free to create your own toy transactions between one another, or actual commerce if you voluntarily choose to do so.

This is definitely not piggybacking on a real concept. I own 2 Resilience servers as Sir Johan Nygren asked me, and publically mind you, on Bluesky to become a part of his jipple.net Resilience server AND he trusted me enough to:

1: extend a 10,000 Swedish Kronor trustline to me.

2: Send me a toy transaction of 100 Swedish Kronor and paying me 2 kronor in taxes; I was the FIRST to receive taxes within the Resilience protocol [my trust index is 2%].

3: He gave me 500$USD for the support over a decade plus of the project.

4. Offered for me to become the second Resilience server administrator within the network’s topology – adding the first Bitcoin based Resilience and CAD$ Resilience servers.

Just that you suggested this is spam / scam content has DEEPLY hurt my feelings and I am just so upset now that you suggested that…

#5 · September 20, 2025, 1:29 am

Quote from johan on September 20, 2025, 1:29 am

Quote from zerpie on September 16, 2025, 4:39 pm

While the underlying academic idea of Resilience is not a scam, these posts have strong hallmarks of scam / spam content, by piggybacking on a real concept.

This spring I solved the “reserve payment attack” which was where Ryan Fugger got stuck in 2006. I presented it in Austria this summer (video here). The idea Ryan had was to use a “gradual penalty” rather than the entire payment all at once (as Lightning network for example does today). The problem he ran into was that he used a 2-phase commit that only had a penalty on one of the phases. And with continuous timeouts you tend to increase the combined time until the payment fully times out, thus undermining the original solution (a timeout). The simple diagram below shows the 3-phase commit very clearly:

My implementation is extremely robust and easy to audit. You can view the code here. It is 2400 lines of code for the entire system. It is extremely minimalistic, based on extremely simple and sound principles.

Since it is a multi-server network in the true sense, there are many servers. Each server is stand-alone. There is no central point of control, there is no central oversight. Taylor has been a pioneer and started two servers, so there are five servers in total. I am running my own account on the domain johan.to (a single-user server).

The currency is not really “pegged” to anything (as I understand, “collateralized” multi-hop payments are just Ripple with payment channel state proofs also done by each user-to-user account, whereas Ripple is just trust-backed), so it is not really “transactions in various currencies including Bitcoin, national currencies, and community tokens” as Taylor writes, it is an unnamed unit of account. It does not have to be more. It does not have payment channel functionality built-in, since the redistribution only makes sense with trust-backed currency (sybil issue only solved then). As far as I can see it is possible for Resilience to be fully compatible with Ripple (of course) and also “collateralized” Ripple (such as backed by Bitcoin, or Ether, or whatever else), you can use the exact same protocol, the 3-phase commit specifically, for all of it, but my own priority is my Resilience system (and with it of course I have already built Ripple Inter Server Protocol, as Resilience required for Ripple to be created first).

With this it is clear the “lets run Ripple on a blockchain” was a prototype just like RipplePay, it let a prototype be up and running without Ryan having to administer it so it was easier for Ryan I guess. Whether or not it has been good or bad I can’t really tell. Interledger has done good work, the vision of a true inter-ledger system is a step forwards, and with my 3-phase commit it can be real.

If you want to test Resilience you can use Taylors servers, or my server https://jipple.net or you can just host your own. In 10-20 years there could be thousands of servers. The software is extremely robust. It should be possible to use for the next couple of decades to run the Resilience network. As I planned since 2012, but as you can see I had to solve the “reserve payment attack” issue first, I was assuming that part (Ripple) was already taken care of by others but it seems I was wrong so I had to do it myself. Peace

Quote from zerpie on September 16, 2025, 4:39 pm

While the underlying academic idea of Resilience is not a scam, these posts have strong hallmarks of scam / spam content, by piggybacking on a real concept.

This spring I solved the “reserve payment attack” which was where Ryan Fugger got stuck in 2006. I presented it in Austria this summer (video here). The idea Ryan had was to use a “gradual penalty” rather than the entire payment all at once (as Lightning network for example does today). The problem he ran into was that he used a 2-phase commit that only had a penalty on one of the phases. And with continuous timeouts you tend to increase the combined time until the payment fully times out, thus undermining the original solution (a timeout). The simple diagram below shows the 3-phase commit very clearly:

My implementation is extremely robust and easy to audit. You can view the code here. It is 2400 lines of code for the entire system. It is extremely minimalistic, based on extremely simple and sound principles.

Since it is a multi-server network in the true sense, there are many servers. Each server is stand-alone. There is no central point of control, there is no central oversight. Taylor has been a pioneer and started two servers, so there are five servers in total. I am running my own account on the domain johan.to (a single-user server).

The currency is not really “pegged” to anything (as I understand, “collateralized” multi-hop payments are just Ripple with payment channel state proofs also done by each user-to-user account, whereas Ripple is just trust-backed), so it is not really “transactions in various currencies including Bitcoin, national currencies, and community tokens” as Taylor writes, it is an unnamed unit of account. It does not have to be more. It does not have payment channel functionality built-in, since the redistribution only makes sense with trust-backed currency (sybil issue only solved then). As far as I can see it is possible for Resilience to be fully compatible with Ripple (of course) and also “collateralized” Ripple (such as backed by Bitcoin, or Ether, or whatever else), you can use the exact same protocol, the 3-phase commit specifically, for all of it, but my own priority is my Resilience system (and with it of course I have already built Ripple Inter Server Protocol, as Resilience required for Ripple to be created first).

With this it is clear the “lets run Ripple on a blockchain” was a prototype just like RipplePay, it let a prototype be up and running without Ryan having to administer it so it was easier for Ryan I guess. Whether or not it has been good or bad I can’t really tell. Interledger has done good work, the vision of a true inter-ledger system is a step forwards, and with my 3-phase commit it can be real.

If you want to test Resilience you can use Taylors servers, or my server https://jipple.net or you can just host your own. In 10-20 years there could be thousands of servers. The software is extremely robust. It should be possible to use for the next couple of decades to run the Resilience network. As I planned since 2012, but as you can see I had to solve the “reserve payment attack” issue first, I was assuming that part (Ripple) was already taken care of by others but it seems I was wrong so I had to do it myself. Peace

Taylor Warden has reacted to this post.

#6 · September 20, 2025, 2:10 am

Johan was kind enough to as well create open registration on jipple.net, he forgot to mention, so if you or anyone else has a problem with trusting me then just use his Resilience server or use your own instance (if interested, Resilience prides itself as a voluntary system of course).

If you require more trust with me or in my Resilience servers, then know that Johan has access to the servers himself as I trust the man explicitly, an not only that, he also has access to my Namecheap account itself for devops needs too. Johan also was the one that setup both Resilience servers; I just managed the purchasing of products (from my IT partner of about 8 years).

I do not know what else to say here about the “piggybacking”? The sites are completely free and without any plans for offering say a membership for extra features, no-no, not even asking for donations to cover domain & VPS lease costs – I will cover that myself as I want to see Resilience flourish! Also, if something were to happen to me, then Johan could carry on with a new admin in my place of these servers.

No worries for the rest of our days,

Taylor.

johan has reacted to this post.