Thread by @PagodaPlatform

Hey #NEAR 👋

Now that we've presented @NEARProtocol's technical protocol roadmap...

We're starting a weekly Roadmap Spotlight! 🔦

We'll do quick break downs of upgrades coming to the protocol, and what they mean for builders and users. Starting with: Meta Transactions 👥🧵

What are meta transactions? 🤔

Also known as gas-less transactions, they enable a third-party (it can be the app itself!), to send a transaction on behalf of another user, and pay for the fee/gas 🤝.

Meaning: dApps could handle transactions for users.

As a user, when you interact with a blockchain like #NEAR, you will probably need to send a transaction to either move funds or use the dApp.

For a new user, that means 📜:

1) Creating a wallet
2) Getting funds
3) Approving the transaction
4) Paying for a gas fee

If you're new to Web3, this experience is far from what you know and are accustomed to.

Meta transactions can help smoothen out that experience on #NEAR, and help onboard users without them needing:

A) To deal with transactions at all.
B) Require funds to use the dApp.

In #NEAR, meta-transactions will be baked at the protocol-level 🥮.

Instead of building it into each contract as a feature, and trusting custom implementations, developers can just tell protocol to delegate a specific transaction.

Simpler to implement, standardized, and safer.

Meta-transactions were proposed in NEP-366, authored by @ilblackdragon

The upgrade has been reviewed by the Protocol Working Group (@NEARDevGov), and is receiving updates based on feedback from the meeting.

See the technical specs & discussion below!
github.com/near/NEPs/pull…

This is one of many upgrades coming to #NEAR to simplify the overall Web3 experience for users and builders. Zero-balance accounts is another one, for example!

Stay tuned, because each week we'll dive into one of these 👋 and explain how they play well together.