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

Well my password is 40 digits long mixture of letters, numbers special digits and does not make any words up. I know it is secure enough but I would prefer cold storage just like my bitcoin on paper wallets and stored in a secure location.

How about creating a secure pass phase u can remember easily ? That's the safest way because people need to hack your brain to gain access. They cant even find any physical print out of your pass.

I know that was keeping passphrase secure etc. But am looking into paper wallet and looking on how to create one and store coins on paper as offline hard paper wallet. Once got guide down think will look into creating paper wallet for bust if I get the time to

There is no need for backup wallet. U don't even need to back up anything if u remember your pass phase. That's the magic of burst. U can access your burst anywhere , anytime , any platform as long as u remember your pass phase. There is no .wallet file to backup. U don't have to import anything. Type in your pass phase and u are good to go. This is not bitcoin. This is burst !

OMG look @diff

It is tough to get started but once you got the simple steps in order like wallet files plotting and so forth it gets simple on the way the ncan go to exchange and buy. Its way under prriced in my option but holding some reserves right now and keeping rest in offline wallet stored on back up hard drive.

Little insight to new guide.



Should soon have the rest done on it have  the first 2 sections done and dusted now working though plotting and mining and a few other bits. Once this is all done then going to go over it for spelling at the min its just rough

legendary.. do you know how hard is to mine this coin and how expensive it is.. so we have BTC at super low , for one BTC one can purchase a semi ok drive of not even high capacity I don't care who is selling but they aint making much profit and off of me they make pennies on the dollar right now

preparing to pick up 213000.00000000 at 202 satoshi , he /she even added 50K to the sell order, 199 sat.. waiting a bit but not too long

damn... can't do exceed a limit.. would have chunked up to 1 million BURST.. got close though.. not selling even 1 , see you soon

Dumpers will dump and hate on it. Am here for the long run and dont intend to dump my stash of more than that. So can only wait and see what the future holds.

And an update regarding guide got a fair bit of it updated and will be hopefully rapping up next weekend and eventually getting the new and improved guide up for everyone and the new starters to get started out

koko doubled his investment just now kind of waited all day long, someone unrolled 250K from mining ops again at 200 satoshi, swallowed it... immediate

let's see.. next bigger lot is 156,960.10747000  he/she wants 202 sat... thinking thinking...

Shit, I was late 

Thanks, this is very helpful!

Websites are not really my thing, but any recommendation is welcome )). A crowdfund project to be active and to start showing the info properly needs at least one transaction (of at least 2 bursts)

Wonderful, now it works 

It would be nice to write hints like "no spaces" and how long it will take to see the Crowdfunding Project Active. That would help

I love this coin

The name should not contain spaces

I tried to create a Crowdfund AT, but it gives an error:

conf/nxt-default.properties

change lines
100 : to
and 107:
to


That should be all

Noto so much!
But you can check here for more details

http://burstcoin.eu

Bye bye

That assembler is currently the best way to compile ATs to bytecode. A precompiled jar of it probably should be made, but if you compile it you just need to pass a filename of assembly code to it and it'll dump the bytecode.

For publishing, in the wallet go to transactions -> ATs, then click Create AT. Set any name and description, paste the bytecode into the code field. If your at expects any data to be already set when it starts you can use the the data field, otherwise leave it blank. data pages * 256 is the number of bytes of space your at has. all variable are 64bit, so you get 32 variables per data page, so pick an appropriate number. call stack pages is only needed if you use call/ret opcodes for subroutines, but same idea as data pages, except its how deep you can nest calls. user stack is only needed for push/pop opcodes, and same idea as call stack. Min activation amount is the minimum amount which must be sent to an at to wake it back up to avoid dust transaction from wasting all its funds on step fees. The fee is the number of pages total(code pages is calculated automatically). if you set it too low it'll say in an error what the min fee for those settings is, so you might as well just submit it with 1, and see what it says and set that. Nothing will run until you send your at some funds for step fees, so after it has confirmed check the list of your ats in the wallet(transactions -> ats) and send it some coins.

There is no dedicated test environment(yet), so for now what we've been doing is taking the wallet source, editing Constants.java and setting DIGITAL_GOODS_STORE_BLOCK, AUTOMATED_TRANSACTION_BLOCK, AT_FIX_BLOCK_2 all to 0, and setting INITIAL_BASE_TARGET higher(add at least 2 0s to the end), edit the config file to remove the seed nodes, and recompile and you'll have a wallet you can instamine on and supports ATs.

I'd really like to know this as I would like to centralize my wallets, I know questions get lost really easily in this thread.

This is awesome news! Glad to see more ATs getting coded up and released into the wild.

Would it be possible for you to provide some detailed instructions on how exactly you go from the assembly code to a published AT? I'm aware of the Scala AT assembler, but I'm not sure exactly what steps to take to actually use the assembler and publish the AT to the Burst network with all the right parameters. Also, is there any test environment for ATs? Thanks!