Skip to content

Crypto payments docs #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
iulianpascalau merged 2 commits into from
Apr 17, 2026
Merged

Crypto payments docs #84

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
65b1cbf
- added crypto-payments docs
iulianpascalau Apr 17, 2026
e9e2e10
- final touches
iulianpascalau Apr 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,24 @@ Inside the Proxmox environment (`pve-R640`), several targeted VMs are provisione
- **Purpose**: Altered node code and scripts repositories, specifically designed for historical data retrieval. The node code is tuned so only the API engine is running, the p2p, blocks syncing, heartbeat and consensus go routines are not started to conserve resources.
- **Local DB**: Yes, LevelDB.

## Crypto Payment Service

A detailed diagram of the crypto payment is presented below:


![Crypto-payments Diagram](crypto-payments.drawio.png)

The process begins when a user wishes to purchase credits (tokens) to access the Deep History infrastructure. Upon navigating to the crypto-payments section of the administration panel, a unique ID is allocated to the user.

Based on this ID, a dedicated private/public key pair is generated and securely managed by the `crypto-payments` service. When any MultiversX wallet deposits EGLD funds into that generated address (provided the amount exceeds the minimum deposit threshold), a background loop inside the service detects the new deposited amount and automatically invokes the `addCredits` smart-contract function via a relayer.

This approach guarantees that all deposited funds are reliably converted into access credits. It also greatly simplifies the user experience, as it removes the need for complex smart contract interactions—only a standard, simple fund transfer is required.

The service code is available on GitHub: https://github.com/iulianpascalau/mx-crypto-payments-go along with the smart contract implementaion: https://github.com/iulianpascalau/mx-credits-contract-rs

**_Note:_** This payment service is highly modular and can be integrated into other systems as a standalone building block. It handles the heavy lifting of seamlessly converting native EGLD deposits into internal tokens or credits utilized for access control.


## Networking & Domains

The Epoch Proxy exposes two external endpoints to interact with the underlying virtual machines:
Expand Down
Loading
Loading