evernodexrpl / evernode-hook Goto Github PK

Numerous people are reporting this error with today's hosting payments.

error : Heartbeat tx error Transaction failed with error tefMAX_LEDGER

@RichardAH and @chalith

As described in Evernode's Whitepaper 1.0:

The Evernode Hook would be configured to broadcast the Node’s details, the 
fact it wishes to be on Evernode, its availability to host dApps, and its willingness 
to be paid in Evers. The Hook would track the Node’s performance so dApps 
can see how reliable it is. This information would be accessed from any XRP 
Ledger-compatible wallet or browser plug-in

As you know, each node wanting to be apart of the Evernode Network and be paid in its native currency in exchange for services can run HotPocket & Sashimono and notify the Evernode Hook itself, this is good but not good enough since there is no real cryptographic proof that the node itself wanted to be apart of the Evernode Network.

To not allow nodes to lie that it did not agree to participate, make it a requirement for them to sign a virtual agreement using their node private key, it wont accualty be a real legal document, just a way to verify that they themselves agreed upon the terms. Something like this:

I, (node public key), agree to be apart of the Evernode Network and serve its users in exchange for Evernode's native currency. The native currency may or may not have any real world value

and a random string of hash attached to the Hook's registry (e.g: SHA256/512) that contains this specific text above including their public key, so every user can reach out to this hash and recall that the node did in fact agree using its own private key.

As much as I hate using this dumb phrase, I'm gonna use it:

Don't trust, verify

https://github.com/HotPocketDev/evernode-hook/blob/f5c97f591eb3c686a1aecf3303e4a32579deef24/src/evernode.c#L53-L54
Why do we need to notify the user that no memos were attached to their transaction?