zhell@moneybutton.com:670122 this one cannot be banned by …

so zhell@moneybutton.com:670122 might actually root to zhell@relayx.io

@255

*route and not root, tired 😅

so we keep the benefit of paymail but add censorship resistance for the cost of adding a 6 digit number

I think the compromise can be interesting

in some cases or after a certain amount of block has passed your timestamped paymail can even be simplified:

zhell@moneybutton.com:680k
or
zhell@moneybutton.com:0.68

which both mean "before block 680000"

and the previously shared ones remain valid

the ' . ' in 0.68 can even be dropped as we can consider that if it starts with a 0 it always mean "0 . "

so we get zhell@moneybutton.com:068

or over time even:

zhell@moneybutton.com:07

or

zhell@moneybutton.com:1

and all of those will alway be valid

actually meant zhell@moneybutton.com:1M here

block # translations:
670k => 670 000
07 => 700 000 (or use 0M7 for clarity ?)
1M => 1 000 000
1M2 => 1 200 000

if you don't include the block # timestamp, then it is still valid also but will directly query the paymail provider, so we only add a new way to route paymails from the blockchain identity

example of the simplification process over time, the wallet would do it for you automatically:
1263256 => 1M26326 => 1M2633 => 1M264 => 1M27 => 1M3 => 2M

Why do you think any paymail server thinks this is true? I know they don't. That address would fail on any server I know of as of now.

this is a proposal so anyone is free to support it or not

Thanks for the clarification.