Author

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

hero member
Activity: 714
Merit: 500
I've known about burst for  while now, seriously considering a "bursting" rig I guess. Anyway to calculate best bang for buck? Obviously storage capacity is king so like 4tb blacks but what gpu for plotting? Does it matter? Thanks in advanced Smiley

Here is the burst calculator - http://burstcoin.eu/calculator.
legendary
Activity: 1330
Merit: 1009
I've known about burst for  while now, seriously considering a "bursting" rig I guess. Anyway to calculate best bang for buck? Obviously storage capacity is king so like 4tb blacks but what gpu for plotting? Does it matter? Thanks in advanced Smiley
legendary
Activity: 1820
Merit: 1001
Does anyone know what has happend to the pool pool.burstcoining.com??
full member
Activity: 182
Merit: 100
Ok,  So ive Finally ploted about 30tb and im starting to feel like the Pools are not paying me appropriately.  So i would like to start solo mining for a bit to compair the payouts.    How do I get my PoC miner to Read from Multiple drives.  as of now the Poc miner Only mines from the Plot folder that the PoCminer.bat is Included in.


I need it to read from about 7 different harddrives.   

Untill Now i was using Uray's Miner in which i was able to simple add the paths to each plot folder in a .cfg file  How do i do the same with POC miner?
legendary
Activity: 1820
Merit: 1001
Now Im on block 60247; Base Target: 1969552 , But still watching some block are with 0 activity

Seems things are speeding up took a while for some of my transactions to show and also confirm once all problems sorted with the updates this coin gonna go too the moon as it's so under priced right now
legendary
Activity: 1512
Merit: 1000
quarkchain.io
Now Im on block 60247; Base Target: 1969552 , But still watching some block are with 0 activity
sr. member
Activity: 462
Merit: 250
Hey,

Today I am going to deploy the first AT use case: The Lottery AT.

I created a new account ( BURST-2Z98-XJU6-A2UA-FDKZP ), which will be used to send funds to the Lottery without participating in the draw. That way we can "kickstart" the lottery with an amount for the first draw to create more interest and winnings for the winner of the first decentralized lottery using AT. So any funds send to that address will be send back to Lottery AT account.

I am thinking the ticket size to cost 2000 burst. The lottery fees for processing the txs are about 15burst. So the final amount to participate to the lottery will be 2015 burst. If you think the ticket amount is too big or too small please say so.

The lottery will pay the winner the total worth of tickets purchased approx. every 1 week plus all extra that were sent to the special address to help seed the Lottery payout

When participating to the lottery, the AT will create a random ticket for you after 15 blocks. The ticket is sent back to the participant through a normal tx with the ticket ( in hex format ) included as a message. Due to a limitation of the AT txs only one ticket can be send back as a message to each participant per block, although if you send more in one block the AT always draws a ticket for each different tx, so that limitation does not mean you will not get more tickets per block per tx if you make multiple purchases.

I created a .html file which needs to be copied under the directory /html/ui/ inside burst folder. After you copy the html file you can use the browser to access it ( http://localhost:8125/atlotteries.html  ). The html displays the lottery state (current winner account, total current winnings e.t.c) and provides also a button for quick ticket purchase.
Here is a screenshot of the resulted .html : https://i.imgur.com/Pz8H2SQ.png

If you are using http://localhost:8125 to access your burst wallet then download this version:
https://mega.co.nz/#!KcZiTBBS!V5SobUhbDGu7Dcw2un1jGszIM3Scl0e3feK9wduKPlU

else if you are using http://127.0.0.1:8125 to access burst wallet this version:
https://mega.co.nz/#!GBhwCTAD!NucXtJh7o9h-4R_gJafnY7xVlgbKJ5IEZ0tA7AYadyM

Also here you can see the lottery's code that will be deployed here : http://pastebin.com/xiDdMzEG

Regards

- vbcs

 


Now when the blockchain seems alright, don't forget to participate in the LuckyAT, BURST's completely decentralized Lottery! As of now the winner will get more than 46,000 BURST, but the sum will increase as tickets are bought.

Just follow vbcs' instruction and you can participate; would you like more information on LuckyAT and Smart Contract, see our recent press releases (where the Sources give important additional knowledge):  
http://burstcoin.info/sc/TheLotteryCase.pdf
http://burstcoin.info/SmartContracts.pdf


Remember, only we who buy tickets decides how much the LuckyAT's winning sum will be - there is no regulation, no cheating, no taxes, just fair - and a bit of luck  Smiley
sr. member
Activity: 286
Merit: 250
With the latest chain download from a few hours ago, my 3 wallets finally made it to the new chain and have stayed there, behaving totally normal. Anyone still having issues might want to download that chain, and then restart their wallet.

Please note that i have not verified the chain is good, is not some sort of clever 50% attack - i'm sure enough it is legit that i don't want to bother cross checking it with the alternative chain to look for differences.

at 60244 now, and basetarget is 1934848 so i would assume most miners are now on the longer chain.
hero member
Activity: 527
Merit: 500
I sure hope the pools manage to get things fixed as am currently starting new plots again due to finding over lap on them lol

Anyone notice any difference in having plots generated and then optimized with  optimizer any difference or improvements ?

Quite large improvement in read time for me, something like 30 seconds less.
legendary
Activity: 1820
Merit: 1001
I sure hope the pools manage to get things fixed as am currently starting new plots again due to finding over lap on them lol

Anyone notice any difference in having plots generated and then optimized with  optimizer any difference or improvements ?
sr. member
Activity: 280
Merit: 250
full member
Activity: 241
Merit: 100
here is the problem report of pool.burstcoin.io (US, SG and EU)

on 26th January 2015, pool suffered (or maybe some others too) from massive forked blockchain
as a result, there are some payments that was made on that forked chain
all of those payments are NOT confirmed by current blockchain network
as a result, pool's wallet API reported wrong balance using API :

Code:
...burst?requestType=getGuaranteedBalance&account=&numberOfConfirmation=1

it reported usable balance from all those transactions as it never happend, but pool can't use those
unspent funds because those transaction already on blockchain but as unconfirmed tx

it can be seen if i open burst wallet using pool account, balance is (for example) 126 burst
but if check it using API above, balance is 37K burst !

the problem is, those transactions seems never be confirmed or rejected up until now,
it still there as a zombie txs

here is the list of tx from my pool

...cut...

i have no idea how to delete those tx or solution for this problem, any hints?

currently pool running on latest 1.2.1, already tried resync the blockchain db from scratch


Hi there Uray, I've experienced the same problem with our pool (based on your code) and did manage to fix it accessing the pool's wallet in debug mode an clearing all unconfirmed transaction.

how do you clear the unconfirmed tx ?

Set "nxt.enableDebugAPI=true"
Go to http://127.0.0.1:8125/test?requestTag=DEBUG and click clearUnconfirmedTransactions

Courtesy of Okae who posted it

Also, great to see you back around here Uray

haaaa... this one is cool!
thank you very much

[---]
currently pool running on latest 1.2.1, already tried resync the blockchain db from scratch


If you try with the one I uploaded to mega, do you still have them?


***EDIT: This one:
https://mega.co.nz/#!xxBW0aAJ!ei9F7kVav87vAIV5ae3Fu8cWtPA4JZIpSFfEy1M7gMg

thanks for the link

after clearing the unconfirmed tx using debug mode, those zombie TXs still coming back again after a few blocks... any clue?

try to stop wallet on the pool, clear transaction, wait a few block and restart it
hero member
Activity: 1400
Merit: 505
here is the problem report of pool.burstcoin.io (US, SG and EU)

on 26th January 2015, pool suffered (or maybe some others too) from massive forked blockchain
as a result, there are some payments that was made on that forked chain
all of those payments are NOT confirmed by current blockchain network
as a result, pool's wallet API reported wrong balance using API :

Code:
...burst?requestType=getGuaranteedBalance&account=&numberOfConfirmation=1

it reported usable balance from all those transactions as it never happend, but pool can't use those
unspent funds because those transaction already on blockchain but as unconfirmed tx

it can be seen if i open burst wallet using pool account, balance is (for example) 126 burst
but if check it using API above, balance is 37K burst !

the problem is, those transactions seems never be confirmed or rejected up until now,
it still there as a zombie txs

here is the list of tx from my pool

...cut...

i have no idea how to delete those tx or solution for this problem, any hints?

currently pool running on latest 1.2.1, already tried resync the blockchain db from scratch


Hi there Uray, I've experienced the same problem with our pool (based on your code) and did manage to fix it accessing the pool's wallet in debug mode an clearing all unconfirmed transaction.

how do you clear the unconfirmed tx ?

Set "nxt.enableDebugAPI=true"
Go to http://127.0.0.1:8125/test?requestTag=DEBUG and click clearUnconfirmedTransactions

Courtesy of Okae who posted it

Also, great to see you back around here Uray

haaaa... this one is cool!
thank you very much

[---]
currently pool running on latest 1.2.1, already tried resync the blockchain db from scratch


If you try with the one I uploaded to mega, do you still have them?


***EDIT: This one:
https://mega.co.nz/#!xxBW0aAJ!ei9F7kVav87vAIV5ae3Fu8cWtPA4JZIpSFfEy1M7gMg

thanks for the link

after clearing the unconfirmed tx using debug mode, those zombie TXs still coming back again after a few blocks... any clue?
sr. member
Activity: 256
Merit: 250
Quick question : Are the original POC miners still supposed to work fine?

i use the java miner for almost 6 month now. it works and finds blocks.
poolminer i dont know.
sr. member
Activity: 286
Merit: 250
Quick question : Are the original POC miners still supposed to work fine?
hero member
Activity: 1400
Merit: 505
here is the problem report of pool.burstcoin.io (US, SG and EU)

on 26th January 2015, pool suffered (or maybe some others too) from massive forked blockchain
as a result, there are some payments that was made on that forked chain
all of those payments are NOT confirmed by current blockchain network
as a result, pool's wallet API reported wrong balance using API :

Code:
...burst?requestType=getGuaranteedBalance&account=&numberOfConfirmation=1

it reported usable balance from all those transactions as it never happend, but pool can't use those
unspent funds because those transaction already on blockchain but as unconfirmed tx

it can be seen if i open burst wallet using pool account, balance is (for example) 126 burst
but if check it using API above, balance is 37K burst !

the problem is, those transactions seems never be confirmed or rejected up until now,
it still there as a zombie txs

here is the list of tx from my pool

...cut...

i have no idea how to delete those tx or solution for this problem, any hints?

currently pool running on latest 1.2.1, already tried resync the blockchain db from scratch


Hi there Uray, I've experienced the same problem with our pool (based on your code) and did manage to fix it accessing the pool's wallet in debug mode an clearing all unconfirmed transaction.

how do you clear the unconfirmed tx ?

Set "nxt.enableDebugAPI=true"
Go to http://127.0.0.1:8125/test?requestTag=DEBUG and click clearUnconfirmedTransactions

Courtesy of Okae who posted it

Also, great to see you back around here Uray

haaaa... this one is cool!
thank you very much

[---]
currently pool running on latest 1.2.1, already tried resync the blockchain db from scratch


If you try with the one I uploaded to mega, do you still have them?


***EDIT: This one:
https://mega.co.nz/#!xxBW0aAJ!ei9F7kVav87vAIV5ae3Fu8cWtPA4JZIpSFfEy1M7gMg

thanks for the link
Jump to: