function at getFirstSendingAddressFromTX (/home/jettscythe/Documents/server/sqlforaction.js:489:34) at Object.sqlforaction.getSQLForAction (/home/jettscythe/Documents/server/s
e/Documents/server/index.js:334:5) at IncomingMessage.<anonymous> (/home/jettscythe/Documents/server/node_modules/bitcoind-rpc/lib/index.js:133:7) at IncomingMessage.emit
attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem
:133:7) at IncomingMessage.emit (events.js:203:15) at endReadableNT (_stream_readable.js:1129:12) at process._tickCallback (internal/process/next_tick.js:63:19)
Agreed, there should be a way to obsolete the old key and inherit data & relationships by the new key, in case of lost of old key.
1.Using my privkey, set an addr as inheritor 2.When old memo pk get hacked, register a new account and import the inheritor key. 3.Use inheritor to announce the obsolete of old key.
Yesterday BCH: 346284-345586=698 memo txs. num of txs📉6.9%, account for 4.0% of all BCH txs(17264) BSV: 727578-727160=418 memo txs, num of txs📉7.9%, account for 8.2% of all BSV txs(5098)