You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 25, 2019. It is now read-only.
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
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
The text was updated successfully, but these errors were encountered: