Presumably, this is where the static withdraw address for each user is stored, along with existing user information.
Something like ALTER TABLE
will be issued to extend the existing database with at least the two new columns:
- a value e.g.
static_withdraw_address_is_configured
(or something more concise) indicating whether the user has configured a static withdraw address, stored as a Boolean (or similar) and initialized tofalse
for all users - a value e.g.
withdraw_address
to hold the user-configured static withdraw address, stored as CHAR(34) (same type as existingaddress
column) and uninitialized by default (it is not to be accessed unless thestatic_withdraw_address_is_configured
). Or, if the datatype has a reliable way for indicating it is uninitialized/invalid, that may be used instead creating thestatic_..._is_configured
column, particularly if doing so is more convenient.
The README.md will need to be updated to add thes