-
Notifications
You must be signed in to change notification settings - Fork 97
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.
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
add get_current_mtp
API call
#1338
Comments
@cipig Could you please provide more input on this? Basically, electrums do not set an MTP in any way, it's calculated in MM2 by requesting recent block headers and using their timestamps. |
@cipig This is ready for testing. @smk762 This is ready for documentation in the dev branch. @borngraced could you please provide information about the new RPC method, please also add it to the postman collection and open a PR to developer-docs. |
The — very useful for debugging some common bugs in mm2 USAGEexample request: {
"method": "get_current_mtp",
"userpass": "USERPASS",
"mmrpc": "2.0",
"params": {
"coin": "KMD"
}
} example response {
"mmrpc": "2.0",
"result": {
"mtp": 1658746383
},
"id": null
} |
@cipig Did you have a chance to test it? |
works fine, checked couple coins, compared to block explorer and the values look fine |
We stumbled upon some electrum servers that set a wrong MTP which then leads to problems like #1281 in mm2.
It would be very helpful to have a
get_current_mtp
API call in mm2, so we can check the electrums for this problem and avoid those that have it and as such don't add them to ADEX Desktop/Mobile config.The text was updated successfully, but these errors were encountered: