When can Burst be listed in some major exchange, it should increase its value and spread the word about them.
which one do you mean by major exchange? |
|
|
|
i am thinking maybe if u mine using java 32 bit it will cap the ram use ?
i'm just using the miner in the "burst-pool-miner r2" folder, dunno about the other pool miner i noticed that the ram usage rise when too much shares are submitted at the same time, something wrong in the code shhh you should fix and mine in secret LOL. so whats' the cause? i am not using java miner myself other than just for testing, so i dont know what happen after long run i am using dcct miner it only use hundreds MB of mem, mining using linux on sempron 145 with 2 GB of RAM, running fine without any issues |
|
|
|
uray, i ask it here also, your miner sucks too many gb of ram when submitting shares, i have filled 2tb and i'm using 6.7gb when submitting, this is crazy
the java miner? or C miner?, which miner is it? i am not sure why, because what i did is just modify "SubmitNonce" network data to original java POCMiner and to C miner from dcct |
|
|
|
also when mining i getting
New best: 6286766055087500646:162129
Submitting share
{"result":"Passphrase does not match reward recipient"}
{"baseTarget":"8530500","height":"9637","generationSignature":
what does Passphrase does not match reward recipient mean ... my wallet and passphase are the same ?
if you want to pool mining, just delete your passphrase.txt , i've seen so many user submiting their secret passphrase to pool, you are lucky i am not thief... |
|
|
|
i've seen on pool we have nonce spammer, who ever doing this it has no use since pool will always pick your best deadline, not add up all your submitted nonce, and also submiting nonce that has higher deadline than your current best deadline will incur penalty to your share as it will flood the network with garbage data
Why do fuckers have to try and game the system? It gets old ya know. Just ban them and be done with it. you are the man ! satoshi nakamoto ... |
|
|
|
|
i've seen on pool we have nonce spammer, who ever doing this it has no use since pool will always pick your best deadline, not add up all your submitted nonce, and also submiting nonce that has higher deadline than your current best deadline will incur penalty to your share as it will flood the network with garbage data
|
|
|
|
@uray please make a separate chat-window
yeah i will, but the most important first, realibility and bug-free |
|
|
|
the port is necessary to set? some users didn't set it
I think it had to be set to 80 if there were firewall issues only. the miner come without the port, i've added it manually, this is why i'm asking umm... better specify it, i am not sure if i set default port on code if port is missing |
|
|
|
I am mining at burst-pool.cryptoport.io but I get this error
{"baseTarget":"8011203","height":"9346","generationSignature":"094196fa421af7d84
399dc8f70812a5111d1060a367eeaabd8e12b70815fc3e2"}
{"baseTarget":"8011203","height":"9346","generationSignature":"094196fa421af7d84
399dc8f70812a5111d1060a367eeaabd8e12b70815fc3e2"}
{"baseTarget":"8011203","height":"9346","generationSignature":"094196fa421af7d84
399dc8f70812a5111d1060a367eeaabd8e12b70815fc3e2"}
New best: 8848628598514937831:4303067
Submitting share
Error: Failed to submit nonce
Error: Unable to get mining info from wallet :http://burst-pool.cryptoport.io/bu
rst?requestType=getMiningInfo
Error: Unable to get mining info from wallet :http://burst-pool.cryptoport.io/bu
rst?requestType=getMiningInfo
Is it because all miners submit new shares at once when a block is found and the server cant handle it?
I have got some payouts so it works but maybe not all shares are received so I am getting less than I should...
I only seem to be getting the error when submitting shares shortly after a new block has been found
have you update ur miner ? please anything related to that pool, post here -> https://bitcointalk.org/index.php?topic=769473.0 |
|
|
|
received PM from nicehash.com would it cool if we can rent/lease disk space on nicehash ? what do you think, should we do this ?  |
|
|
|
Hi uray What happen if i still don't have a chance to update your miner.... Will your previous miner still work ? my id BURST-P6ZR-UMNC-P42F-8GRH5 yup it will work |
|
|
|
ok here is the update for http://burst-pool.cryptoport.ioI hope recent problem of "failed to get mining info from wallet" and error while "submiting nonce" is reduced, it seems that java wallet can't handle spamming of submitNonce from hundreds miners at the same time, so I ended up running 4 wallet in round-robin. for confusion about not getting paid, everything is OK, i did check it, and for more information that currently pool minimum payout is 250 BURST, that is you will get payment to your wallet when your balance on pool reach 250 BURST, you can see your balance on right-most column on "Current Round Shares" panel ok its confusing to look at the UI, I will make an improvement. and if you dont see your balance, or your balance is '--', that is your balance is zero, zero balance sometime means that your share is not converted to burst balance yet, so you should check how much share credit you own on second rightmost column both on "Current Round Shares" and "All Round Shares" panel. your shares will be converted into burst balance when pool has positive balance, after conversion if your burst balance is more than 250, then you will get paid, if not, your burst will deposited to your pool balance and your shares credit will be zero (as it already converted into burst) some important to note here that your share credit is always reducing every block, there are share expiration of 50% every block, this is to give most recent shares a higher value than the shares that have lesser contribution in block found round. but your burst balance is never reduced, so if your share is already converted to burst you are safe just wait until it reach more than 250 burst. more shares will be converted into burst if pool found blocks more often, everytime we found a block, all existing shares will be converted to burst. Great! Thanks for looking into the submitNonce issue. I am back on your server now and it looks like the issue is better, but I still see occasional failures. Perhaps you could set a high limit on deadlines to reduce the load further? Even something like 500,000 would help considerably, wouldn't it? Even 1,000,000 limit on deadline would help and those shares are only worth ~3 BURST. PS. I love your GUI! I hope you do not change it too much  the problem is, miner only submit nonce and accountid to pool and pool's wallet calculate how much is the deadline based on his nonce and accountId, these calculation is heavy if we have hundreds at the same time the difference with official pool (the one dev used) is on dev's pool these calculation is done on miner side, and miner only submit their nonce if deadline is within limit, but the downside is on official pool you need to run wallet locally, while on me, you just need to run miner without wallet running is ok. |
|
|
|
I have a concern about the Burstcoin mining process and it possibly being susceptible to selfish mining attacks. I'm hoping that the dev, or someone more familiar with the mining process can alleviate my concerns.
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Unlike most coins that try to find a nonce where hashing the block contents meets a target, burst includes information proving an address is eligible to mine that block, and then signs it with that address. This allows us to lock down the numbers used in the calculations by only using information from previous blocks in the algorithm. The only information that is used is generation signature, block height, and the user who mined the last block, so the only manipulation possible is to choose not to mine a block you are able to. The generation signature is based on the same values from the block before it. Changing the transactions won't change anything, so that isn't a valid attack vector. Ok, thanks for the explanation! I think I am getting a better understanding of how it all works. However, this brings up another concern. Does this mean that the transactions themselves aren't encoded in the blockchain in any way? If that's the case, then it seems it would be trivial to perform double-spends. Sorry if this is a stupid question! The transactions are in the block, and the block's transactions are part of the hash that is done while the miner is signing the block, it's just that the transactions don't affect whether that miner is eligible to mine that block. Ah, ok good. So, the transactions are an input into the generation signature, which I think means that the transactions affect which miner is eligible to sign the next block, correct? If so, it seems a selfish mining attack is still possible, but rather complicated. A malicious miner could choose a transaction set which manipulates the generationSignature such that when they do find a block, they're also almost guaranteed to find the next block. I still feel like I must be missing something :/ Dev, can you comment on this? generation signature is shabal256(lastblock.generationsignate concat lastblock.miner) scoop is chosen with shabal256(generationsignature concat blockheight) modulous 4096 deadline is calculated shabal256(scoopcontents concat generationsignature) / basetarget transactions are never factored into eligability. u r genius dev... thats why we dont have merkleroot to hash... |
|
|
|
i sold all my burst! i think we are going probably down to 300
Sure! And i have seen a flying horse right out of my house talking about football with a cat. Burst crashes on C-Cex.  Well. If you're not a newbie: -3 millions+ coin mined every day -2 billions coins total -No investor -Only miner -Millions of burst on c-cex deposit. You always go with the flow, do you? As they say, misery loves company. Negative people will try to bring down positive people. The problem is people listen to people like IE, Bobsurplus, etc....Strange the few can motivate the many to do things that are illogical and rash actions. People forget to trust their own wisdom and become followers to the wrong people/cause. As far as the price is going down, we can only blame us for pushing it down like that, no excuses. You know how the crypto world goes, there can be 100 billion coins and people can hype a coins price without any real reason/ideal. So, this BS of people making a big deal about the minting of the coin per day, then why is DOGE and REDD still around. Both are doing ok still with their larger amount of coins. My advise, if your here to dump, then dump and leave this thread with your negative comments/ideals. I really don't understand why you people like to stroke your ego when you so call predict a coins lower prices/downfall, your not Nostradamus. So, stop with thinking your some professional economist/stock broker, because that wouldn't fly in the Stock Market with rumors/FUD. +1. Best comment since a while +1 nice comment, this forum should have upvote like reddit does |
|
|
|
ok here is the update for http://burst-pool.cryptoport.ioI hope recent problem of "failed to get mining info from wallet" and error while "submiting nonce" is reduced, it seems that java wallet can't handle spamming of submitNonce from hundreds miners at the same time, so I ended up running 4 wallet in round-robin. for confusion about not getting paid, everything is OK, i did check it, and for more information that currently pool minimum payout is 250 BURST, that is you will get payment to your wallet when your balance on pool reach 250 BURST, you can see your balance on right-most column on "Current Round Shares" panel ok its confusing to look at the UI, I will make an improvement. and if you dont see your balance, or your balance is '--', that is your balance is zero, zero balance sometime means that your share is not converted to burst balance yet, so you should check how much share credit you own on second rightmost column both on "Current Round Shares" and "All Round Shares" panel. your shares will be converted into burst balance when pool has positive balance, after conversion if your burst balance is more than 250, then you will get paid, if not, your burst will deposited to your pool balance and your shares credit will be zero (as it already converted into burst) some important to note here that your share credit is always reducing every block, there are share expiration of 50% every block, this is to give most recent shares a higher value than the shares that have lesser contribution in block found round. but your burst balance is never reduced, so if your share is already converted to burst you are safe just wait until it reach more than 250 burst. more shares will be converted into burst if pool found blocks more often, everytime we found a block, all existing shares will be converted to burst. |
|
|
|
ok here is the update for http://burst-pool.cryptoport.ioI hope recent problem of "failed to get mining info from wallet" and error while "submiting nonce" is reduced, it seems that java wallet can't handle spamming of submitNonce from hundreds miners at the same time, so I ended up running 4 wallet in round-robin. for confusion about not getting paid, everything is OK, i did check it, and for more information that currently pool minimum payout is 250 BURST, that is you will get payment to your wallet when your balance on pool reach 250 BURST, you can see your balance on right-most column on "Current Round Shares" panel ok its confusing to look at the UI, I will make an improvement. and if you dont see your balance, or your balance is '--', that is your balance is zero, zero balance sometime means that your share is not converted to burst balance yet, so you should check how much share credit you own on second rightmost column both on "Current Round Shares" and "All Round Shares" panel. your shares will be converted into burst balance when pool has positive balance, after conversion if your burst balance is more than 250, then you will get paid, if not, your burst will deposited to your pool balance and your shares credit will be zero (as it already converted into burst) some important to note here that your share credit is always reducing every block, there are share expiration of 50% every block, this is to give most recent shares a higher value than the shares that have lesser contribution in block found round. but your burst balance is never reduced, so if your share is already converted to burst you are safe just wait until it reach more than 250 burst. more shares will be converted into burst if pool found blocks more often, everytime we found a block, all existing shares will be converted to burst. |
|
|
|
BURST-RBEU-3SN6-RWLF-52ZQG
how much i have on pool ?
0 BURST , 25.3 share, first share received at block #8899 (currently #8902) |
|
|
|
unofficial pool isn't displaying the diff anymore on the miner? you changed it?
yeah i optimized it a bit, since lot of users get "unable to receive mining info from wallet" its because of http request timeout, and that request of "getMiningInfo" is sent every second by all miners, multiply that by 100 miners on the pool, and add up another type of request... ok, there is still the infamous error aout not submitting nonce choose port 8124 or 80, which one is better for you, meanwhile i am still optimizing net traffic |
|
|
|
|
Show Posts
