Bitcoin Forum
July 25, 2017, 07:03:47 PM *
News: BIP91 seems stable: there's probably only slightly increased risk of confirmations disappearing. You should still prepare for Aug 1.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 [874] 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 ... 1287 »
  Print  
Author Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000  (Read 1973577 times)
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 27, 2015, 10:55:39 AM
 #17461

I would like the PR team to please get their terminology straight about the "smart contracts" as some of the articles I've read are just plain wrong.

For a start please use the term AT - Automated Transaction(s) when referring to the "smart contract" technology (i.e. what flavour of "smart contracts" does Burst use) and a specific use case (or "smart contract") such as the Lottery AT.

Thus "smart contracts" would be the most general term - so you'd say that "our platform has implemented AT for its smart contracts" (vs. say Ethereum).

An "Atomic Cross-Chain Transfer" is just a use case (it is not a technology like AT is) so don't confuse that (treat ACCT just as you do the Lottery).

It would also be appreciated if "created by CIYAM Developers" could be included in the PR material about AT as we really do need to try and get other coins to also adopt AT (so that we can actually start using ACCT ATs) and we have no PR team ourselves.


Thanks, we will be more careful with the terminology! As for credits for AT we always link to your site in the sources, but "created by CIYAM Developers" is of course possible to include in the material write (or get to check before publishing) Smiley

When in comes to journalists though we learned the hard way that some doesn't even contact us before publication, despite we end each press release with contact info and "Looking forward to hear from you!". Can't do much there, but hopefully it will get better if we are stricter with the concepts used.

Regard,

1501009427
Hero Member
*
Offline Offline

Posts: 1501009427

View Profile Personal Message (Offline)

Ignore
1501009427
Reply with quote  #2

1501009427
Report to moderator
1501009427
Hero Member
*
Offline Offline

Posts: 1501009427

View Profile Personal Message (Offline)

Ignore
1501009427
Reply with quote  #2

1501009427
Report to moderator
1501009427
Hero Member
*
Offline Offline

Posts: 1501009427

View Profile Personal Message (Offline)

Ignore
1501009427
Reply with quote  #2

1501009427
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
CIYAM
Legendary
*
Offline Offline

Activity: 1848


Ian Knowles - CIYAM Lead Developer


View Profile WWW
January 27, 2015, 10:59:59 AM
 #17462

@mmmaybe - much appreciated - we are in this together and hopefully AT and Burst will be a successful combination (both myself and vbcs are very pleased with how AT has been integrated with Burst).

Looking to making more history with an actual "atomic cross-chain transfer" hopefully happening within the next month!

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 27, 2015, 11:01:40 AM
 #17463

Burstdev, is it ok if we re-organize the OP a little bit? Make it easier to edit for you and some new resources. If ok, I'll PM you something in like 12h.

Would be nice to mention LuckyAT or the lottery in the subject line but I see that it's already long...


catbref
Member
**
Offline Offline

Activity: 86


View Profile
January 27, 2015, 11:03:52 AM
 #17464

Beta pool at pool.burstcoining.com:8124 is back up. Looks like the wallet was upset due to that v1.2.0 fork so I cleaned out unconfirmed transactions and rescanned the blockchain.
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 27, 2015, 11:06:44 AM
 #17465

@mmmaybe - much appreciated - we are in this together and hopefully AT and Burst will be a successful combination (both myself and vbcs are very pleased with how AT has been integrated with Burst).

Looking to making more history with an actual "atomic cross-chain transfer" hopefully happening within the next month!


That would be amazing with a ACCT so soon! vbcs and I was talking about trying crowdfunding, and I might have a case. Are you on irc? I'll contact you by email or PM otherwise.

CIYAM
Legendary
*
Offline Offline

Activity: 1848


Ian Knowles - CIYAM Lead Developer


View Profile WWW
January 27, 2015, 11:10:52 AM
 #17466

Are you on irc? I'll contact you by email or PM otherwise.

I use Skype mostly so you can PM me to get my Skype id.

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
catbref
Member
**
Offline Offline

Activity: 86


View Profile
January 27, 2015, 03:05:48 PM
 #17467

I'm seeing NXT log entries like this:
Code:
2015-01-27 14:41:42 INFO: tx with id 0 found
2015-01-27 14:41:42 INFO: Transaction to 4697159292272720752 amount 0

Plus I submitted a transaction to my wallet, called getUnconfirmedTransactionIds then getTransaction on that transaction only to be told:
Code:
{\"errorDescription\":\"Unknown transaction\",\"errorCode\":5}

Possible race condition in the wallet software?
mtwelve
Legendary
*
Offline Offline

Activity: 966


Bitcoin Journalist PM for more info


View Profile WWW
January 27, 2015, 03:10:20 PM
 #17468

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

The plotter is for Plotting your hard drives,   This is what creates the file you will mine from.  The plotting software you use Has no effect on your mining.   For a while GPU plotter was the fastest way to plot drives  but atm i think Wplotter is King,  Atleast its was for me.

Simple answer to your question,  No.  The plotter you use has no effect on your mining.  Simple the speed of your plotting which can take weeks depending on how much HD space you have to Fill!

So is the way I described above with 4tb hard drives the best way to go?

vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 27, 2015, 04:07:17 PM
 #17469

I'm seeing NXT log entries like this:
Code:
2015-01-27 14:41:42 INFO: tx with id 0 found
2015-01-27 14:41:42 INFO: Transaction to 4697159292272720752 amount 0

Plus I submitted a transaction to my wallet, called getUnconfirmedTransactionIds then getTransaction on that transaction only to be told:
Code:
{\"errorDescription\":\"Unknown transaction\",\"errorCode\":5}

Possible race condition in the wallet software?

These are AT txs, 4697159292272720752 is account number. When an AT program seeks for a tx after a timestamp and there is none you see that debug message. These outputs will be removed in next releases.

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
bensam123
Sr. Member
****
Offline Offline

Activity: 424


View Profile
January 27, 2015, 04:14:27 PM
 #17470

Another question, if you're plotting with the GPU plotter with 'direct write' so it optimizes and plots at the same time, how much slower does it go then normal plotting? It also looks like it freezes when you start plotting, but it's still writing to the disk, no status text is updated. Does stagger size matter with 'direct write'? If it's properly defraged couldn't you effectively have a stagger size of like 1024 and it wouldn't matter?

Bump on this... It takes so long to plot, a few questions help a lot.
Merick
Full Member
***
Offline Offline

Activity: 128


View Profile
January 27, 2015, 04:41:16 PM
 #17471

Another question, if you're plotting with the GPU plotter with 'direct write' so it optimizes and plots at the same time, how much slower does it go then normal plotting? It also looks like it freezes when you start plotting, but it's still writing to the disk, no status text is updated. Does stagger size matter with 'direct write'? If it's properly defraged couldn't you effectively have a stagger size of like 1024 and it wouldn't matter?

Bump on this... It takes so long to plot, a few questions help a lot.

https://burstforum.com/index.php?threads/gpu-plot-generator.45/
This thread should answer your questions.

Specific details in the middle of that thread
https://burstforum.com/index.php?threads/gpu-plot-generator.45/page-12#post-3252

Hopefully these conversation can move to the forum and off of this thread for better organization.

Good-Luck
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 27, 2015, 05:10:47 PM
 #17472

New article, front page on a major crypto site: "What happened to Ethereum?"...

https://www.cryptocoinsnews.com/cryptocurrency-burst-makes-smart-contracts-reality-happened-ethereum/
Quote
One of the promising applications of the block chain technology are smart contracts. Different startups have been working on launching smart contracts, like Ethereum, but it would appear that a small crypto startup has beaten everyone else to it.

 Grin

Their tweet:

Quote
CryptoCoinsNews @CryptoCoinsNews  ·  6h 6 hours ago

Cryptocurrency BURST Makes Smart Contracts a Reality, What Happened to Ethereum? https://www.cryptocoinsnews.com/cryptocurrency-burst-makes-smart-contracts-reality-happened-ethereum/

CCN claims to have more than 12,000 on their email list and 300,000 unique visitors. They have +23,000 followers on Twitter.





xizmax
Hero Member
*****
Offline Offline

Activity: 526


View Profile
January 27, 2015, 05:19:32 PM
 #17473

New article, front page on a major crypto site: "What happened to Ethereum?"...

https://www.cryptocoinsnews.com/cryptocurrency-burst-makes-smart-contracts-reality-happened-ethereum/
Quote
One of the promising applications of the block chain technology are smart contracts. Different startups have been working on launching smart contracts, like Ethereum, but it would appear that a small crypto startup has beaten everyone else to it.

 Grin

Their tweet:

Quote
CryptoCoinsNews @CryptoCoinsNews  ·  6h 6 hours ago

Cryptocurrency BURST Makes Smart Contracts a Reality, What Happened to Ethereum? https://www.cryptocoinsnews.com/cryptocurrency-burst-makes-smart-contracts-reality-happened-ethereum/






146 Shares already. Nice work mate!

BURST, your C:\urrency
Follow us on https://twitter.com/burstcoin_dev
bensam123
Sr. Member
****
Offline Offline

Activity: 424


View Profile
January 27, 2015, 05:23:08 PM
 #17474

Another question, if you're plotting with the GPU plotter with 'direct write' so it optimizes and plots at the same time, how much slower does it go then normal plotting? It also looks like it freezes when you start plotting, but it's still writing to the disk, no status text is updated. Does stagger size matter with 'direct write'? If it's properly defraged couldn't you effectively have a stagger size of like 1024 and it wouldn't matter?

Bump on this... It takes so long to plot, a few questions help a lot.

https://burstforum.com/index.php?threads/gpu-plot-generator.45/
This thread should answer your questions.

Specific details in the middle of that thread
https://burstforum.com/index.php?threads/gpu-plot-generator.45/page-12#post-3252

Hopefully these conversation can move to the forum and off of this thread for better organization.

Good-Luck

I already checked through that thread and read the relevant posts. It doesn't answer the above questions though as I was asking for other peoples experience with direct write and stagger size with direct write. That thread is also not active, so it's sorta pointless to post there.

Also, I finished optimizing one of my plots using the optimizer. However the newly 'optimized' plot is now smaller then the old plot by 5GB and of course the sizes don't match when I start up blagos miner. Is this normal? Did something go wrong along the way?

Hmmm... after adjusting the name of the file it only finishes 3s faster then the old plots (also it appears to be corrupt now).
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 27, 2015, 05:30:43 PM
 #17475

New article, front page on a major crypto site: "What happened to Ethereum?"...

https://www.cryptocoinsnews.com/cryptocurrency-burst-makes-smart-contracts-reality-happened-ethereum/
Quote
One of the promising applications of the block chain technology are smart contracts. Different startups have been working on launching smart contracts, like Ethereum, but it would appear that a small crypto startup has beaten everyone else to it.

 Grin

Their tweet:

Quote
CryptoCoinsNews @CryptoCoinsNews  ·  6h 6 hours ago

Cryptocurrency BURST Makes Smart Contracts a Reality, What Happened to Ethereum? https://www.cryptocoinsnews.com/cryptocurrency-burst-makes-smart-contracts-reality-happened-ethereum/


CCN claims to have more than 12,000 on their email list and 300,000 unique visitors. They have +23,000 followers on Twitter.


146 Shares already. Nice work mate!

Gonna contact them about an error in the article, yes, really nice that we are getting noticed!

Merick
Full Member
***
Offline Offline

Activity: 128


View Profile
January 27, 2015, 06:11:54 PM
 #17476

Another question, if you're plotting with the GPU plotter with 'direct write' so it optimizes and plots at the same time, how much slower does it go then normal plotting? It also looks like it freezes when you start plotting, but it's still writing to the disk, no status text is updated. Does stagger size matter with 'direct write'? If it's properly defraged couldn't you effectively have a stagger size of like 1024 and it wouldn't matter?

Bump on this... It takes so long to plot, a few questions help a lot.

https://burstforum.com/index.php?threads/gpu-plot-generator.45/
This thread should answer your questions.

Specific details in the middle of that thread
https://burstforum.com/index.php?threads/gpu-plot-generator.45/page-12#post-3252

Hopefully these conversation can move to the forum and off of this thread for better organization.

Good-Luck

I already checked through that thread and read the relevant posts. It doesn't answer the above questions though as I was asking for other peoples experience with direct write and stagger size with direct write. That thread is also not active, so it's sorta pointless to post there.

Also, I finished optimizing one of my plots using the optimizer. However the newly 'optimized' plot is now smaller then the old plot by 5GB and of course the sizes don't match when I start up blagos miner. Is this normal? Did something go wrong along the way?

Hmmm... after adjusting the name of the file it only finishes 3s faster then the old plots (also it appears to be corrupt now).

Benchmark Comparison - Direct vs Buffer - https://burstforum.com/index.php?threads/gpu-plot-generator.45/page-11#post-3014
Why Direct is Slower than Buffer - https://burstforum.com/index.php?threads/gpu-plot-generator.45/page-11#post-3034

Plot size will remain the same after optimization, if it is not then something went wrong along the way.  Did you run out of disc space?

Information about Stagger setting when Direct Plotting - https://burstforum.com/index.php?threads/gpu-plot-generator.45/page-13#post-3348
During a direct right method, the stagger setting is used to setup a ram buffer for pre-ordering of the nonces.

In your example, a stagger size of 1024 during a direct right method will just use 1024KB of RAM for the nonce buffer re-ordering.
In this thread and the thread on the forums a few people have complained about the reliability of the direct right method, also the performance hit for direct right compared with just plotting and optimizing does not appear to be worth it.

Maybe someone else can add some information to this topic.

Just because no one has posted in the BurstForum thread about the GPU plotter doesn't mean it's dead.  This seems like the perfect type of question to ask in a Burst forum within the GPU plotter post.  I'm guessing the regulars have had their questions answered you would be a perfect candidate to awaken the thread and maybe Cryo will answer your questions directly
pinballdude
Sr. Member
****
Offline Offline

Activity: 286


View Profile
January 27, 2015, 07:07:58 PM
 #17477

(edit)

running the 1.2.1 precompiled jar gives me other results than running my compiled version of 1.2.1, using my fork at github, which *should*'ve been updated with the 1.2.1 on the burst github.

I will compare sources and trace back and see what's the cause, either i merged in something in a bad way, or i didn't pull stuff out correctly, or the compile process itself was wrong somehow, or perhaps the jar in the 1.2.1 archive has not been built with the exact 1.2.1 sources on github. Will go hunt for answes and be back once i know what i did wrong. Until further notice, you can assume i made an error somewhere.

my fork stumbles upon block 60414, while the burst.jar in the 1.2.1 distro has no issues with that block.


sorry for all the noise... just kinda confused, never had this kind of problem before.



→→→→→→→→→→→→→→→→→→ 💰 Hard-Disk Mineable Cryptocurrency !! B U R S T C O I N 💰 Cheap Price & Easy to Invest - CHECK IT OUT NOW! !! →→→→→→→→→→→→→→→→→→ 💰 Asset exchange, Automatic transactions, Escrow system & More !!
xizmax
Hero Member
*****
Offline Offline

Activity: 526


View Profile
January 27, 2015, 07:14:57 PM
 #17478

Currently on 60524 here, no issues. Sorry for not being of much help :/

BURST, your C:\urrency
Follow us on https://twitter.com/burstcoin_dev
Blago
Sr. Member
****
Offline Offline

Activity: 416



View Profile
January 27, 2015, 07:22:31 PM
 #17479

stuck again, this time at 60413 which is my latest block , and it matches exactly the one at the block explorer that is current - however, i get no more blocks than that, and that's on all 3 wallets again.

If i am alone having this problem, i'll revert to the pre-built 1.2.1 to see if that is better.  all 3 wallets are showing errors like this, and it seems that these errors always show up when my chain stops being updated :

Code:
2015-01-27 20:04:14 INFO: tx with id 1488316772753571631 found
2015-01-27 20:04:14 INFO: get timestamp for tx with id 1488316772753571631 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2015-01-27 20:04:58 INFO: tx with id 1488316772753571631 found
2015-01-27 20:04:58 INFO: get timestamp for tx with id 1488316772753571631 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
2015-01-27 20:05:21 INFO: tx with id 1488316772753571631 found
2015-01-27 20:05:21 INFO: get timestamp for tx with id 1488316772753571631 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

i will now try to revert to the precompiled burst.jar on one of the pc's and see if that fixes the problems. if it is, it's just me having broken my burst fork. i suspect not though, but who knows, perhaps i merged in 1.2.1 in a bad way, missing something important. Anyone else stuck at 60413?, and what wallet version are you using?


sorry for all the noise... just kinda confused, never had this kind of problem before.

i have same messages, but daemon works fine



nxt.wellKnownPeers=198.199.103.145; 178.62.39.204; burst.cryptoport.io; 192.155.252.202; 37.58.107.74; 119.81.165.138; 119.81.44.170; 119.81.44.171

Relax, I’m russian!...
BURST-B2LU-SGCZ-NYVS-HZEPK
crazyearner
Legendary
*
Offline Offline

Activity: 1666



View Profile
January 27, 2015, 09:10:31 PM
 #17480

Beta pool at pool.burstcoining.com:8124 is back up. Looks like the wallet was upset due to that v1.2.0 fork so I cleaned out unconfirmed transactions and rescanned the blockchain.

Nice to see your back up and running you should become active in Burst irc chat so that people can keep in contact with you if something happens and can update memebers.
Pages: « 1 ... 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 [874] 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 ... 1287 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!