-
m-relay
<9d74bfb0:monero.social> Just wanted to make sure: wallet->account->address
-
m-relay
<9d74bfb0:monero.social> is there anyway to get the current wallet?
-
selsta
what exactly do you want from the wallet?
-
selsta
seed, private keys, file name, file location, ...?
-
m-relay
<9d74bfb0:monero.social> I was just trying to know the order of possession
-
m-relay
<rogu157:matrix.org> Hi,
-
m-relay
<rogu157:matrix.org> I am a pool operator, and I want to create unique work for all my miners.
-
m-relay
<rogu157:matrix.org> Here's the algorithm I currently use:
-
m-relay
<rogu157:matrix.org> 1. Parse the block template blob.
-
m-relay
<rogu157:matrix.org> 2. Place unique extra data into the coinbase transaction.
-
m-relay
<rogu157:matrix.org> 3. Calculate the merkle root.
-
m-relay
<rogu157:matrix.org> 4. Send the hashing blob to the miner.
-
m-relay
<rogu157:matrix.org> I apply this approach to all connected miners.
-
m-relay
<rogu157:matrix.org> However, if the block contains many transactions from the mempool, calculating the merkle root takes time.
-
m-relay
<rogu157:matrix.org> As a result, the last miner receives their work with a latency that can affect our pool's profits because part of the block time is spent on creating the work.
-
m-relay
<rogu157:matrix.org> I would like to know if there is another way to create unique work assignments or any optimizations for the algorithm we are currently using.
-
m-relay
<rogu157:matrix.org> And another question:
-
m-relay
<rogu157:matrix.org> Is it acceptable for the Monero network if we mine empty blocks for a few days to check if there is a profit problem due to the unoptimized work creation in our source code?
-
m-relay
<rogu157:matrix.org> This would be just for a few days, and we would revert to normal operations afterward.
-
m-relay
<rogu157:matrix.org> Hi,
-
m-relay
<rogu157:matrix.org> I am a pool operator, and I want to create unique work for all my miners.
-
m-relay
<rogu157:matrix.org> Here's the algorithm I currently use:
-
m-relay
<rogu157:matrix.org> 1. Parse the block template blob.
-
m-relay
<rogu157:matrix.org> 2. Place unique extra data into the coinbase transaction.
-
m-relay
<rogu157:matrix.org> 3. Calculate the merkle root.
-
m-relay
<rogu157:matrix.org> 4. Send the hashing blob to the miner.
-
m-relay
<rogu157:matrix.org> I apply this approach to all connected miners.
-
m-relay
<rogu157:matrix.org> However, if the block contains many transactions from the mempool, calculating the merkle root takes time.
-
m-relay
<rogu157:matrix.org> As a result, the last miner receives their work with a latency that can affect our pool's profits because part of the block time is spent on creating the work.
-
m-relay
<rogu157:matrix.org> I would like to know if there is another way to create unique work assignments or any optimizations for the algorithm we are currently using.
-
m-relay
<rogu157:matrix.org> Thank you!
-
sech1
rogu157 Merkle root can be recalculated in O(logN) time, and P2Pool can create work for 10k miners in ~0.01 seconds
-
sech1