Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 329. (Read 2171083 times)

Today i received nothing. :-(

Thank you ! And what's the utility of this memory ?

certainly... 0.25% of amount

Did burstbank pay today?

Currently the only miner that is noticed is Blago, we will add functionality for other miners soon.

edit- actually, it looks like cat already added uray and java miners too.

The memory size when ploting is expressed in nonces (256KB) not MB. So to get 6144MB, you need to multiply by 4 - so use 24,576 instead. And I'd normally aim for closer to 50% rather than 75%

H.

@smaxer

add Runaurufu-miner to http://burstcoin.eu/downloads

https://burstforum.com/index.php?threads/windows-mining-guide.14/page-5#post-2891
https://mega.co.nz/#!GgJgHKyL!bgDSAYkOXXrl4i7nISPucvdRjvW0RyhiYpVMQzCPKeg

I've got a little problem when I try to plot. I followed the crowetic's guide and when I set 75% of my memory (the total is 8192 MB so 75% is 6144 Mb), it says me not 6144 MB of memory used but 15XX MB of memory used (I forgot the XX number but it isn't very import, you can see that it isn't the same number). To hit the 6144 MB of memory used, I need to put a number close to 18000. What's the problem ? Can you help me ?

Or nothing better than pool`s target deadline.

So if I've 0 sdl/rdl , I mined nothing ?

tex81 is correct. it should say 64 bytes

hi burst bank.

Can you update the pie chart on http://burstbank.com/index.php with wallets number?

for example:

BurstBank: 18.1%
Coins: 125290311
Wallets: 12345

many thanks!!!

have a nice day!

I think that the scoop is 32-bytes, but for the deadline calculation it used 2 scoops (64-bytes), the calculated and the next one.

sdl - sent deadlines
rdl - recieved confirms deadlines
ss - sent getMiningInfo to server
rs - recieved getMiningInfo from server
(0) - errors
after 999 counters sets to 0

"Server": "burst.ninja".
If the miners will use "InfoAddr": "127.0.0.1" instead of "burst.ninja", sometimes will display incorrect information about Winner (or "no info yet"). This will be the case at the forks in the pool and local wallet...

I see that crowetic uses poolmining for a miner . . .

Possible bank idea (Sorry to make it so lengthy):
One major issue with a Burst bank is trusting the third party and determining the source of income for the interest because there are no loans by the bank.  It has been proposed that there are CD equivalent accounts where penalties for withdrawing early are used toward the interest rate.

My addition would be to use a pool as a bank.  A portion of the pool fee(slightly higher than normal fee to give a decent interest rate) would go toward interest and the normal rewards from mining would be diverted as deposits to an account owned by the trusted pool owner.  The length of the CD would be randomly chosen between a set amount of time to prevent mass withdrawals at once.  The penalty on withdrawals could scale down based on the time remaining in such a way that the penalty is 0% after 90% of the contract.  When the contract reaches completion, it would be automatically renewed for another randomly chosen amount of time (6-8 months?).  If someone decides to take a penalty and withdraw early, the additional funds would go toward a higher interest rate for that period. 

The trick part is securing the bank.  As catbref has already mentioned, removing public access to the wallet would help.  Even better, the funds should be sent to a separate account with a 2048+ character passphrase. Withdrawals are also difficult and I am sure could be done with smart contracts.  For security reasons, I think it would be better for the pool owner to make payouts manually.  The random interval on contract length would hopefully limit this number to about 10 per day.  Requests for payment could be made by PM on this forum, sending a message on the blockchain, or some other way.

Possible addition:
Owners with large amounts of BURST and almost no mining equipment could deposit money into the bank to earn interest.  This would take money away from the pool fee of legitimate miners, but it would encourage the whales (refers to size of wallet, not belt size) to keep their money longer for the interest.  In most cases, someone who bought a bunch of BURST without mining probably plans to do a mass dump in the future unless they have a reason to grow that amount (similar to POS with penalties or POSp?).  Potentially, the more BURST in the bank, the longer the contract length at the same interest rate.  This would force the whales to take a large penalty for mass dumping or grit their teeth with minor market fluctuations. 

As we have learned with any hacked exchange or accounts with large sums of money, security is the biggest concern.  It might even be necessary for the pool owner to have a separate account for every X (say 10) account holders or X% of total to reduce the security risk.  If one wallet is compromised, the attacker would not get as much and the funds could be covered by the pool owner. 

If someone picks up this idea, it would be nice if they gave me a small portion of their pool fee, but unfortunately not a requirement. 

Just a heads-up to let people know the port for mining is 8124 (not 8125 or 80) and port 80 is really for UI/webpage stats.
Also, I'd like to remove public access to the pool's wallet in the near future so change your InfoAddr appropriately too please!

"poolmining" is some miner that uses "pool-mining" as the secretPhrase when it submits nonces - I've not yet worked out which miner that is!

I've suggested adding HTTP headers to nonce submissions like:

X-Miner: Blago v1.150328
(format should be obvious here)

X-Capacity: 13000
(integer GB)


So the whole request might look like:

Just want to bring this up again.


Any updates on 'Decentralized Bank' AT? 


Totally agree that would be awesome!
Btw. thanks sooo much for the daily interest, i will keep my gentlemen's agreement to hold :-)

On blago's miner, what's the ss and rs number in the bottom of the cmd ? The number of shares ?