SetTombstoneAddress
have been, obviously, responsible for setting tombstone address :) And I think we shouldn't change its prototype as you don't set tombstone's address relying on expiration epoch.
Not a big deal, but the prototype with return values (epoch uint64, found bool, err error)
(has -> found
) looks more natural for Go. WDYT?
The nesting can be more than 2 (theoretically).
Getting meta from origin (if it's present) should be enough for ape
The method is no longer actual as I used the approach suggested by @dstepanov-yadro
You have removed only the last line and it affected first line although there is no changes in JS. It seems it didn't have linefeed after the comment? And we should add it after js?