Developer & Node operator resources

The idea of this section is to help provide you with a great first step into the world of developing smart contracts and applications for WAX. There are a lot of resources available on a lot of different places, I hope you can utilize this as a good first step to learn more.

The Basics

Smart Contract Language: C++

NFT Standards

Mainnet Details

Testnet Details

Different APIs

Developer Portals

Check Status for Public WAX Endpoints

Incorporating WAX to your website

There are available tools to help you manage multiple wallets for your website, or you can choose to implement just one of them.
Depending on your frontend, which tool(s) you choose to implement will vary. 

EOSIO UAL (Website Wallet Manager)
WAXJS for websites (Integrate WAX Cloud Wallet)

Base tool to interact with the WAX Cloud wallet. It's built on EOSJS, where you can find further documentation.

Anchorlink for websites (Integrate anchor wallet)

Anchor is the most popular self-management wallet for any Antelope (EOSIO) Blockchain, including WAX. It has support for Ledger, Trezor and more.

Wharfkit - Multiwallet Session manager for websites By Greymass

When I add this in 2023-04, the Wharfkit suite of tools is in early release, so keep up to date with updates. 

Game Development

Many of the above tools and services suits game development well, in this section it will be those created for game development.

WAX Unity SDK

Developer chats

Telegram
Discord

Misc Links

Guides on running nodes

My guides and information

Ross Dold - eosphere - Working with WAX series

  1. Set Up - Testnet node: https://medium.com/eosphere/wax-technical-how-to-1-4cc5c9aa8d4e
  2.  WAX Snapshots: https://medium.com/eosphere/wax-technical-how-to-2-db45a339e735
  3. Set Up - Testnet Block Producer: https://medium.com/eosphere/wax-technical-how-to-3-78d358c46146
  4. Set Up - Mainnet Node: https://medium.com/eosphere/wax-technical-how-to-4-886c5bfaf7b9
  5. Set Up - Reliable Load Balancer: https://medium.com/eosphere/wax-technical-how-to-5-14671fcc7122
  6. Mitigate API Abuse: https://medium.com/eosphere/wax-technical-how-to-6-5e5318a9eb8e
  7.  Set up - State History Node: https://medium.com/eosphere/wax-technical-how-to-7-9ccc102efd9d
  8. WAX Files and Folders: https://medium.com/eosphere/wax-technical-how-to-8-42011a30de1e
  9. Set up - Atomic API node: https://medium.com/eosphere/wax-technical-how-to-9-f7d22bfa4e2b
  10. Optmize & Restore Atomic API node: https://medium.com/eosphere/wax-technical-how-to-10-90c6445632ed
  11. Optmize Ram & Disk Utilization: https://medium.com/eosphere/wax-technical-how-to-11-43695f583e89
  12. Add custom permissions: https://medium.com/eosphere/wax-technical-how-to-12-9d39257d319
  13. Route API traffic: https://medium.com/eosphere/wax-technical-how-to-13-448b3375516
  14. Websocket support on load balancer: https://medium.com/eosphere/wax-technical-how-to-14-b8912d3ba1ef
  15. Hyperion History API
    1. Hyperion Full History Node: https://medium.com/eosphere/wax-technical-how-to-15-1-d2936d3c58d4
    2. Hyperion Software Components: https://medium.com/eosphere/wax-technical-how-to-15-2-a042ea8bc4b4
    3. Configure Hyperion Components: https://medium.com/eosphere/wax-technical-how-to-15-3-b188c6aa9d12
    4. Run Hyperion Full History: https://medium.com/eosphere/wax-technical-how-to-15-4-f735d4cbc197
    5. Clustering Elasticsearch: https://medium.com/eosphere/wax-technical-how-to-15-5-6ae01ea6bf62
    6. Fix Missing Blocks in Hyperion: https://medium.com/eosphere/wax-technical-how-to-15-6-622ae2936771
    7. Hyperion Indexer scaling: https://medium.com/eosphere/wax-technical-how-to-15-7-ce11fbc97c40
    8. Hyperion Streaming with Load Balancer: https://medium.com/eosphere/wax-technical-how-to-15-8-396dd3b0484b
  16. Visualize metrics from WAX Load Balancer: https://medium.com/eosphere/wax-technical-how-to-16-a64d5a53d770
  17. Securely peer through Wireguard VPN: https://medium.com/eosphere/wax-technical-how-to-17-d0fa0961ff58

Leave a Reply

Your email address will not be published. Required fields are marked

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}