search

metacartel / Harbour-MVP

Building a decentralised p2p meta-tx relayer network [MVP] Codename: Harbour ## We solved this problem: https://medium.com/tabookey/1-800-ethereum-gas-stations-network-for-toll-free-transactions-4bbfc03a0a56
https://medium.com/tabookey/1-800-ethereum-gas-stations-network-for-toll-free-transactions-4bbfc03a0a56
MIT License
30 stars 15 forks source link

Definition of the language we use #8

Open pet3r-pan opened 5 years ago

pet3r-pan commented 5 years ago

Tenzorum's definitions

Meta-tx (Meta transaction): Tx with additional meta data fields eg. reward details

Relay: Act of sending meta-tx away to offchain 2nd layer / service node

Relayer: The user / dapp that is sending the tx away to the 2nd layer service node

Delegation: The act of relaying a meta-tx and relaying the reponsibility of executing the tx to a third party

Delegated-tx (Delegated transaction): Meta-tx that has been relayed to a service node to be executed

Service node: A server that recieves meta-txs and executes valid meta-txs

Tx-pool: Pending layer of meta-txs that are ready to be executed

Gasless transaction: And event that happens from the user's point of view

lightclient commented 5 years ago

I think the usage of relay and relayer are very confusing. If you look up the definition of relay it says:

relay (v.) to receive and pass on

The key in the definition is the receiving portion. I believe that because a relayer should receive data, the term should be used to describe what are now called service nodes. The user / dapp are not relaying any data, they are the original source.

My proposal:

Relay: act of executing the tx on the user's behalf Relayer: server that receives meta-txs and executes valid meta-txs Delegation: act of sending meta-tx away to off chain 2nd layer / service node Delegate Contract: a smart contract that can issue txs for an approved user