Skip to content
This repository has been archived by the owner on May 25, 2019. It is now read-only.

Definition of the language we use #8

Open
pet3r-pan opened this issue Sep 27, 2018 · 1 comment
Open

Definition of the language we use #8

pet3r-pan opened this issue Sep 27, 2018 · 1 comment

Comments

@pet3r-pan
Copy link
Member

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
Copy link

lightclient commented Sep 29, 2018

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants