Skip to main content

3 posts tagged with "engineering"

View All Tags

· 3 min read
Tian Pan

Mar 8th, 2024 San Francisco. Payton is excited to work with Network3 to streamline its global payment experiences. Network3 is striving to build a dedicated AI Layer2 and its globally-scaled brandwidth-sharing service takes a global payment solution to empower the customers to pay and get paid easily.

What is Payton

Payton is a Financial OS for ambitious Web3 organizations and freelancers, featuring crypto payment checkout, payroll, payouts, expense management, and automation for freelancers and teams. Payton is built by a team powered by - An industry leading marketplace in Move, Rust, and EVM Blockchain Web3 APIs, which is serving 6K developers, $45 million USD stakes, and 28 blockchains.

What is Network3

Network3 is an AIoT layer 2 platform focused on privacy security and efficient decentralized computing, providing confidential data transfer and computing algorithm sharing for decentralized AI. Network3 integrates an efficient anonymous certificate-less sign-cryption (CLSC) algorithm, a data correctness verification mechanism, an IP anti-tracking measure, and a decentralized reliable federated learning (FL) framework.

Network3 already has mature web2 products with millions of users per month. Network3 will leverage existing web2 traffic and bring users into their web3 innovative ecosystem. The decentralized federal learning AI model training system also generates an incentive mechanism to distribute rewards according to the participant's contribution.

How does Payton’s solution work with Network3?

Organization Setup

Payton will setup the pilot user and product registration for Network3. However, here is a quick preview of what the registration will be like -

Payin - Customers pay Network3

1. Try to pay: Customers using Network3 mobile or desktop app, and want to top up their accounts.

2. Redirect customers: Then the customer will be redirected to[email protected]&price=price_JiGFdJ2Gxf2QUDrHyww7 according to the pricing plan they selected.

3. Pay with various crypto: Customers can pay with various tokens as long as the market value is matching the price.

4. Webhook after payment: Once payment is made successfully, Payton server will issue a receipt to the customer’s email

and call the Network3 server with a body of the following format:

interface IPaytonWebhook {
id: string;
type: "invoice.payment_succeeded";
data: {
customerEmail: string;
planId: string;

Then the the Network3 server can add credits to the customerEmail’s account.

5. Redirect back: Meanwhile, the customer will see a button “Payment succeeded” and clicking that button will redirect back to the pre-registered success URL.

Payout - Network3 pays VPN servers

Network3 specifies what blockchain network they are using and then prepares tokens in the custodial wallet. Then

  1. Record usage increment with Payton server
  2. If needed, Network3 can fetch current usage or invoice for a certain user

Payton server will pay out according to the usage using tokens in the custodial wallet every day.

Other Integrations

Nework3 will use Payton for other corporate financial use cases as well. More integrations are coming.


Payton's partnership with Network3 is a testament to the power of collaboration in the blockchain ecosystem. It underscores the transformative impact that innovative, decentralized solutions can have on global payment systems, setting a new standard for privacy, security, and user empowerment in the digital age. As the boundaries of what's possible continue to expand, the collaboration between Payton and Network3 will likely be remembered as a pioneering step towards a more interconnected and decentralized world.

· 2 min read
Tian Pan

Today we are glad to announce the Payton demo mode now available at Payton is still a work in progress. We are adding pay-in, payout, and team management features. However, here is a demo of what we are working with the company network3 to pilot the crypto checkout use case.

Getting Started

Upon logging in, you'll be greeted with the Home dashboard, presenting a snapshot of your organization's recent activities. This dashboard serves as your command center, offering insights and quick access to various functionalities.

Navigate to the Products section via the side navigation to discover a list of previously registered products. Here, you can effortlessly manage your offerings, setting names and prices to align with your business strategy.

The Checkout Experience

After tailoring your product details, the Checkout button will lead you to the next step. The checkout page is where the magic happens: add your contact information, select your preferred cryptocurrency, and send tokens to the designated address. It's as simple as that.

Following payment confirmation, the checkout session concludes, smoothly transitioning customers to their next interaction.

Advanced Integration: Listening for Payment Success

For developers aiming to integrate payment notifications, the Developers tab is your go-to. Input your webhook URL to receive HTTP POST requests upon successful transactions, keeping your server in the loop.

The request body follows a structured format, ensuring you receive pertinent information without hassle:

interface IPaytonWebhook {
id: string;
type: "invoice.payment_succeeded";
data: {
customerEmail: string;
planId: string;

Wrapping Up

Our demo offers just a glimpse into the efficient, user-friendly world of crypto checkouts facilitated by Payton. We're on a mission to refine and enhance this product, making digital payments more accessible than ever. Keep an eye on our Twitter for the latest updates and breakthroughs in crypto payment solutions.

· 3 min read
Mike Thrift

Hello and welcome back to our blockchain blog! Today, we will be diving into an exciting new proposal called ERC-4337, which introduces account abstraction to Ethereum without requiring any consensus-layer protocol changes. Instead, this proposal relies on higher-layer infrastructure to achieve its goals. Let's explore what ERC-4337 has to offer and how it addresses the limitations of the current Ethereum ecosystem.

What is ERC-4337?

ERC-4337 is a proposal that introduces account abstraction to Ethereum through the use of a separate mempool and a new type of pseudo-transaction object called a UserOperation. Users send UserOperation objects into the alternative mempool, where a special class of actors called bundlers package them into a transaction making a handleOps call to a dedicated contract. These transactions are then included in a block.

The proposal aims to achieve several goals:

  1. Enable users to use smart contract wallets with arbitrary verification logic as their primary accounts.
  2. Completely remove the need for users to have externally owned accounts (EOAs).
  3. Ensure decentralization by allowing any bundler to participate in the process of including account-abstracted user operations.
  4. Enable all activity to happen over a public mempool, eliminating the need for users to know direct communication addresses of specific actors.
  5. Avoid trust assumptions on bundlers.
  6. Avoid requiring any Ethereum consensus changes for faster adoption.
  7. Support other use cases such as privacy-preserving applications, atomic multi-operations, paying transaction fees with ERC-20 tokens, and developer-sponsored transactions.

Backwards Compatibility

Since ERC-4337 does not change the consensus layer, there are no direct backwards compatibility issues for Ethereum. However, pre-ERC-4337 accounts are not easily compatible with the new system because they lack the necessary validateUserOp function. This can be addressed by creating an ERC-4337 compatible account that re-implements the verification logic as a wrapper and setting it as the original account’s trusted op submitter.

Reference Implementation

For those interested in diving deeper into the technical details of ERC-4337, a reference implementation is available at

Security Considerations

The entry point contract for ERC-4337 must be heavily audited and formally verified, as it serves as a central trust point for the entire system. While this approach reduces the auditing and formal verification load for individual accounts, it does concentrate security risk in the entry point contract, which must be robustly verified.

Verification should cover two primary claims:

  1. Safety against arbitrary hijacking: The entry point only calls an account generically if validateUserOp to that specific account has passed.
  2. Safety against fee draining: If the entry point calls validateUserOp and passes, it must also make the generic call with calldata equal to op.calldata.


ERC-4337 is an exciting proposal that aims to introduce account abstraction to Ethereum without requiring consensus-layer protocol changes. By using higher-layer infrastructure, it opens up new possibilities for decentralization, flexibility, and various use cases. While there are security considerations to address, this proposal has the potential to greatly improve the Ethereum ecosystem and user experience.