Adamcolton: /* Payment */

2018-04-13T13:58:54Z

Payment

← Older revision		Revision as of 13:58, 13 April 2018
Line 7:		Line 7:
	This is one of the big hurdles I'd like to overcome, but I'm not sure it's even possible.		This is one of the big hurdles I'd like to overcome, but I'm not sure it's even possible.

	I'd like for there to be a way for relay nodes to get a small payment for each message they route.		I'd like for there to be a way for relay nodes to get a small payment for each message they route. Ideally, given A→B→C, each can see some payment token. When B submits their token, it validates payment to A. That way A can't take the money and not forward the transaction.

	[[Category:Dist.ribut.us]]		[[Category:Dist.ribut.us]]

Adamcolton: Created page with "== Mix-net Routes == === Erasure Codes === For A→B, when the packet is sufficiently large (>~10kB) instead of sending directly through a single route, the message can be..."

2018-04-13T13:40:14Z

Created page with "== Mix-net Routes == === Erasure Codes === For A→B, when the packet is sufficiently large (>~10kB) instead of sending directly through a single route, the message can be..."

New page

== Mix-net Routes ==

=== Erasure Codes ===
For A→B, when the packet is sufficiently large (>~10kB) instead of sending directly through a single route, the message can be broken up into several smaller pieces and each is sent through it's own mix-net route. Enough of these will correct for transmission failures.

=== Payment ===
This is one of the big hurdles I'd like to overcome, but I'm not sure it's even possible.

I'd like for there to be a way for relay nodes to get a small payment for each message they route.

[[Category:Dist.ribut.us]]

Dist.ribut.us Transmission - Revision history

Adamcolton: /* Payment */

Adamcolton: Created page with "== Mix-net Routes == === Erasure Codes === For A→B, when the packet is sufficiently large (>~10kB) instead of sending directly through a single route, the message can be..."