Change Details

T3060 Support for adding and removing pending aliases from a dedicated pending aliases collection redis is used to store pending aliases in cache. pending alias registrations are cached for a max of 6 hours. pending alias registrations that become valid alias registrations are removed from the cache. pending aliases are added to the cache on app startup.

T3060 Support for adding and removing pending aliases from a dedicated pending aliases collection Caching is introduced so that tipHeight is available inside the added to mempool event. It would be available from `serverState` in the database, but deemed impractical to make a database call on every incoming tx (could be a huge throughput of these) for a value that only changes every 10 minutes on avg. pending alias registrations that become valid alias registrations are removed from the cache. pending aliases are added to the cache on app startup. pending aliases that go more than 6 confirmations without becoming confirmed or otherwise cleaned up are dropped from the pending collection to prevent unbounded growth.

T3060 Support for adding and removing pending aliases from a dedicated pending aliases collection redis is used to store pending aliases in cache.Caching is introduced so that tipHeight is available inside the added to mempool event. It would be available from `serverState` in the database, pending alias registrations are cached for a max of 6 hoursbut deemed impractical to make a database call on every incoming tx (could be a huge throughput of these) for a value that only changes every 10 minutes on avg. pending alias registrations that become valid alias registrations are removed from the cache. pending aliases are added to the cache on app startup. pending aliases that go more than 6 confirmations without becoming confirmed or otherwise cleaned up are dropped from the pending collection to prevent unbounded growth.