|
The dcct merge tool should probably check for errors during its reads and writes. About 6 hours ago, it seems to have stopped writing out the merge on the 2.1TB plot I was running it on, but it's still burbling through the merges without complaint...
|
|
|
|
I want everyone to know that this guy has been PMing me wanting to buy my drives for $320 but he won't come up to $340. And he wants my plots and user id and password, etc. Cheap ass.
Actually, the intention in my latest offer was to buy them through ebay at the listed price of $340. The extra conditions were to make it worth my while to hand the extra money over to ebay, since they'll give you less than the $320 in escrowed bitcoin I originally offered. i dont get it, why would anyone want to mine on someones other (old) passphrase..
how can he be sure you dont empty that acc? its worth of few spared hours of plotting?? ...
Reward assignment. It's not perfect, but I was trusting Tim not to be a dick about it. Also, this is something Tim appeared to offer in an earlier post: So you're giving your wallet passcode with that bundle too then ;P
Whoever buys them gets it all. |
|
|
|
Timk225, if you go rant in the c- cx troll box until you drive the burst price below 130s, I will buy your drives.  |
|
|
|
|
I'll buy any amount of burst for 110s. Escrow via btcrow.com, I'll pay the fee.
|
|
|
|
Got some stuff reconfigured, attached drives to a different PC. Reinstalled 13.12 drivers. Now I am trying to use 'GPU plot generator v2.1.1'. It gets to --->
Creating OpenCL program
[ERROR] Unable to open the source file
did you install AMD SDK again as well together with 13.12 drivers? When I get this error, it is because the kernel files are not where the plotter is expecting. Where is the kernel subdirectory, relative to your current working directory at the time you run the plotter? |
|
|
|
Thanks. Any body got something else they think that burst needs? (Not things we need Uray for, but rather easy things that I can do)
A chart showing the distribution of recent block winners ( like this) would be useful for verifying the democratizing effect of PoC. |
|
|
|
WTB burst. Large number 250k and above
I wouldn't want to send my burstcoins to someone who clearly doesn't respect them. |
|
|
|
I am using java miner and I get nothing but deadlines of 30,000 years+ after optimising.
If your system can handle it, I would try running two miners in parallel, one with just the plot you ran the optimizer on and one with the just the optimized plot. If there's a problem, you should get different deadlines after both plots have been fully searched. |
|
|
|
i optimized my plots but after optimization can not find share on any pool uray/v2 just seeking and no share for hours and i repoloted with gpu ploter and after 2 min it starts to submiting shaares so i think optimizer not working and messed my plots  Try solo mining the optimized plot with the java miner. I think if your scoops have been misplaced, it should tell you you've got the wrong passphrase. |
|
|
|
Id/nonce/passphrase is submitted the wallet with submitNonce.
submitNonce takes 2 or 3 parameters: secretPhrase, nonce, acctountId
If solo mining, secretPhrase and nonce are sufficient.
If pool mining, the pool's secretPhrase is submitted, and the miner(who is reward assigned to the pool)'s accountIt is sent along.
The wallet returns json with 1 or 2 fields: result is a string. if result is "success", deadline is also present
The wallet will store work submitted to it, and automatically create a block when one of the deadlines it has reach 0.
Thank you. |
|
|
|
|
Could someone please point me to the code in the published pool miner which allows the pool owner to submit a reward-assigned block to the local wallet?
|
|
|
|
As long as the AMD has AVX/AVX2, it should do very well with the optimized cpu plotter. Very impressive that it does gpu plotting speed on certain cpus.
It's not actually that surprising.The GPU mode is still kind of buggy on my graphic card (an old GeForce 9300M GS), don't know the exact reason yet. Sometimes it works, sometimes not. I will try to fix this issue tomorrow. I would never say never, but I am quite skeptical about the nonce computation ever being modified for major speed gains on current GPUs. It requires each thread to crawl over every part of a 256k buffer while computing shabal hashes for all of it, and the cores on top-end GPUs only contain 64kb of memory. I can't see any way to avoid a huge amount memory bandwidth. This is a different problem than for scrypt (where you can trade the memory for extra computation), in that it actually requires access to the memory, or perhaps some fast way to find shabal preimages. |
|
|
|
|
If I have rewardassignment.html set to a different address, can I solo mine? Should I provide the passphrase for the recipient address to the miner?
|
|
|
|
I am solo mining found a block a few days ago. 9500 burst in my wallet. version 1.1.2 I sent 2 burst to Poloniex 3 days ago as a test.
It never showed up. The (first) burstcoin that you have received must to be "confirmed" 1440 times  ( to be used... ) . I think redsn0w must be pulling your leg. You should open a ticket with Poloniex. |
|
|
|
currently i am working on payment system for merchant and escrow service that accept burst as a currency, and also figuring out how to integrate it with burst asset exchange and market You've talked to the dev about this, right? I think he's working on something similar, might be scope for collaboration. as dev plan for file storage, i think its better off start small first, like storing wallet contact into blockchain instead of local wallet I think this is a really challenging problem. It's worth reading the safecoin whitepapers about this to see some of the potential difficulties. and also we could use burst blockchain like torrent tracker or something, future is bright y know
and also i am thinking about using burst node as CDN service Safecoin is also a good place to look for ideas about this. Interestingly, it looks like the first notion of proof-of-capacity arose as a way to secure such a service. |
|
|
|
Community i need your help ... im trying to keep the price of BURST at 200 satoshi ... but i cannot do it alone ... so we need more buy pressure ... as u can se at poloniex and c-cex i already buy 200k BURST alone ...
If u care about this coin you need to buy ... trust me 200 satoshi is a good price ... it can easy go to 500
Let the price rise according to the nonfinancial value the coin is expected to provide. Manipulating the price to sex it up financially is unethical and shortsighted. |
|
|
|
In my opinion Seagate is worst brand, WD is better and Hitachi is king?
I've got some seagates which are absolutely dire in terms of write performance: 40 MB/s over USB 3. I think they are fine for mining, though. I have also read that the poor performance comes from the external enclosure, and if you rip the SATA disk out from it you can get pretty good bandwidth. |
|
|
|
Burst will likely fall to 50 satoshi by Saturday and then 0 sat by the end of next week. Cut your loss now before its too late
Feed the whales and regret your decision in few months
Well, clearly no one here knows the right way to do a debut on bittrex, I'll give you that. :-) PLEASE let the price fall to 50s! PUH-LEAZE!! |
|
|
|
|
Yeah, I'm optimizing one now. Unfortunately I can only afford an SSIZE of 8, it's going to take about a week to optimize a 2.4TB plot, and I have about 30TB of plots. The stagger on these plots is 7500, which was optimal for my GPU, but that's looking like a false economy now.
The limiting factor at the moment is writes. I'm getting about 40MB/s for writing out the optimized plot.
|
|
|
|
|
I only tried a mining pool for a few hours before giving up on it. When I was getting those messages, it was because the pool network was hosed. I also saw extremely long deadlines when I tried to telnet to the mining pool ports directly.
The "no deadline" messages look perfectly normal to me for a 4TB drive. I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times. In your first "no deadline" message, the block was found before you had finished scanning your HD. In the second, it had only just started scanning the drive.
|
|
|
|
|
Show Posts
