You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DMO Monitor needs a table to store miner configuration information.
My initial thought is we should have a table structure as follows, but this is a ROUGH DRAFT and will initially only support solo mining options. Pool changes to be added later.
table miners
id int not null auto_increment primary key,
user_id int
miner_ident_string varchar(64), (see #13)
display_name varchar(64),
miner_config_id int
// NOTE I think we might have some default configs that any user could utilize
// In that case user_id would be null
// If solo is true then pool_id would be left as null...
// If solo is false fullnode_id would be null as would starting_diff
table miner_configs
id int not null auto increment primary key,
user_id int
solo bool
pool_id int
miner_opts varchar(128) (eg "GPU,179200,32,0,0")
fullnode_id int
starting_diff int
receiving_address_id int
table fullnode_configs
id int not null auto increment primary key,
user_id int
node_url varchar(64)
node_user varchar(64)
node_pass varchar(64)
table pool_configs
id int not null auto increment primary key,
user_id int
pool_user varchar(64)
mode varchar(32)
server varchar(32)
port varchar(6)
The text was updated successfully, but these errors were encountered:
DMO Monitor needs a table to store miner configuration information.
My initial thought is we should have a table structure as follows, but this is a ROUGH DRAFT and will initially only support solo mining options. Pool changes to be added later.
table miners
id int not null auto_increment primary key,
user_id int
miner_ident_string varchar(64), (see #13)
display_name varchar(64),
miner_config_id int
// NOTE I think we might have some default configs that any user could utilize
// In that case user_id would be null
// If solo is true then pool_id would be left as null...
// If solo is false fullnode_id would be null as would starting_diff
table miner_configs
id int not null auto increment primary key,
user_id int
solo bool
pool_id int
miner_opts varchar(128) (eg "GPU,179200,32,0,0")
fullnode_id int
starting_diff int
receiving_address_id int
table fullnode_configs
id int not null auto increment primary key,
user_id int
node_url varchar(64)
node_user varchar(64)
node_pass varchar(64)
table pool_configs
id int not null auto increment primary key,
user_id int
pool_user varchar(64)
mode varchar(32)
server varchar(32)
port varchar(6)
The text was updated successfully, but these errors were encountered: