Well, it says Welcome to your new BURST account. So my password is not correct. But I have a .txt file with my password in it on my desktop. How it is possible I cannot log in on my old account?
Copy paste not working?
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 719. (Read 2171056 times)
September 27, 2014, 03:40:47 AM
Copy paste not working?
September 27, 2014, 03:38:37 AM
Well, it says Welcome to your new BURST account. So my password is not correct. But I have a .txt file with my password in it on my desktop. How it is possible I cannot log in on my old account?
September 27, 2014, 03:37:24 AM
Is C-Cex down?
Yes... way to much trading of Burst probably 
lol...I doubt that....
Probably a server issue....
i found on their twitter account a link to this explaination about what has happened to another coin some days ago.
https://bitcointalksearch.org/topic/m.8957857
hopefully this is an isolated issue like they state.
maybe they currently run a database check in relation to this and took the site offline till its done.
September 27, 2014, 03:34:33 AM
But I can't see history of my transactions. There is nothing in there.
is the account id still the same?
September 27, 2014, 03:29:31 AM
But I can't see history of my transactions. There is nothing in there.
your passphrase IS your wallet. Make sure you have entered passphrase correctly otherwise it will create a completely new wallet if you made a mistake typing.
September 27, 2014, 03:25:53 AM
But I can't see history of my transactions. There is nothing in there.
September 27, 2014, 03:20:44 AM
I had old wallet 1.1.2 now there is 1.1.3.
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
yes, that will do the trick, moved through several versions already like that and never had any problems
or you could send it to an exchange
September 27, 2014, 03:16:37 AM
I had old wallet 1.1.2 now there is 1.1.3.
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
yes, that will do the trick, moved through several versions already like that and never had any problems
September 27, 2014, 03:13:24 AM
I had old wallet 1.1.2 now there is 1.1.3.
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
Yes just move "burs DB" an start new wallet. If it does not upgrade, than clear cache.
September 27, 2014, 03:11:02 AM
Is C-Cex down?
Yes... way to much trading of Burst probably lol...I doubt that....
Probably a server issue....
September 27, 2014, 03:10:24 AM
I had old wallet 1.1.2 now there is 1.1.3.
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
How can I upgrade wallet without losing coins?
By moving folder burst_db from wallet 1.1.2 to 1.1.3?
September 27, 2014, 02:58:03 AM
Is C-Cex down?
Yes... way to much trading of Burst probably September 27, 2014, 02:51:59 AM
Is C-Cex down?
September 27, 2014, 01:58:48 AM
New client Burst 1.1.3
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
Did you remember to inform the exchanges of the mandatory wallet update this time?
September 27, 2014, 01:39:36 AM
A picture tells a thousand words. Possible to create an inforgraphics that explain how it works ?
Try the section "Multisignature storage" here. It gives an animation of how it works in one simple application, securing an account so that it would normally require the signature of both the owner and a third party to execute a transaction from it, making it much harder to steal funds because now you have to steal two keys, and one of those keys is in the hands of an entity for whom security is a professional concern.
The explanation is for bitcoin, but the same principles almost certainly apply here (I haven't looked at the new client, yet.)
September 27, 2014, 01:35:38 AM
New client Burst 1.1.3
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
A picture tells a thousand words. Possible to create an inforgraphics that explain how it works ? U work so hard for this but without an image guide (simple to understand) u wasted your effort because less people will know how to use it. U can take look around here, most people cant figure out some of the things here. An inforgraphics that explain how feature works its good for everybody and increase the user rate for this new feature and increase exposure for burst because people who are new only take a couple of second to look at things. An image can capture a person attention faster than wall of text .
An inforgraphics that explain how the feature works is as importance as the feature itself. Its like creating a bombastic feature that nobody use because not many people take a lot of time to read. An inforgraphics will increase the effectiveness of launching the new feature as well as increase awareness for burst. All good advertisement goes with an image. Burst right now lack of PR and this is a good chance to increase awareness of burst. If we miss this chance , we have to wait for another new update which might be weeks or months away.
That's the responsibility of all of us who DO get it, not the dev, he is working hard, leave him to it!
September 27, 2014, 01:12:12 AM
New client Burst 1.1.3
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
download: https://mega.co.nz/#!e15TQRCZ!k043rrfCzkTofW0ICbfq_j269x9zYTShOs2KdWAtaT0
sha256: 201a8491f33c03ffad2d7f9c43f14a6a287e146c8d0a7ac2ae3581f8f8831fcf
Or get it from github.
Update is required.
Instead of picking a block number to fork on in advance, this update will be enabled when I set the alias "featureescrow" to the value "enabled" This allows me to wait longer if necessary for more people to update their clients. It will be at least 3-4 days before this is triggered.
After updating, you will need to refresh your wallet, and possibly clear your cache if things don't look right.
This update adds escrow transactions. You will be able to create escrow transactions where you can list accounts that can sign off on the transfer, and set how many need to sign off to complete the transaction one way or the other. For example, you could create a transaction to another user and list 5 accounts as signers, and require 3 of them to sign to take action. If both the sender and recipient are honest, the transaction can be settled with either the sender releasing the funds, or the recipient refunding them. If the transaction does not go as planned, the 5 signers can announce their decision to the network. If any 3 announce decisions that are in agreement about how to handle the funds(release/refund), it will complete the transaction accordingly. Up to 10 signers can be listed on a transaction, and 1 - 10 signatures can be required for settling. A deadline and action(release/refund/split) are also set when creating the transaction, which will be executed if the deadline runs out to avoid burning the funds if the transaction is never settled. There is a listing in the wallet of all escrow transactions you are involved in(sender, recipient, or signer), that you can click on and select decisions from a drop down menu to easily resolve escrows, and there is a form in the wallet to easily create them. More details will be given on the exact use when I enable the feature.
A picture tells a thousand words. Possible to create an inforgraphics that explain how it works ? U work so hard for this but without an image guide (simple to understand) u wasted your effort because less people will know how to use it. U can take look around here, most people cant figure out some of the things here. An inforgraphics that explain how feature works its good for everybody and increase the user rate for this new feature and increase exposure for burst because people who are new only take a couple of second to look at things. An image can capture a person attention faster than wall of text .
An inforgraphics that explain how the feature works is as importance as the feature itself. Its like creating a bombastic feature that nobody use because not many people take a lot of time to read. An inforgraphics will increase the effectiveness of launching the new feature as well as increase awareness for burst. All good advertisement goes with an image. Burst right now lack of PR and this is a good chance to increase awareness of burst. If we miss this chance , we have to wait for another new update which might be weeks or months away.
September 27, 2014, 12:34:14 AM
Hello, and attention all miners of burstpool.ddns.net
Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.
NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.
--Irotniga
Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.
NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.
--Irotniga
Also you can use alias:
HardInvest
to send burst.
September 27, 2014, 12:31:07 AM
Am I correct in saying that a passphrases.txt is not needed in a folder when pool mining? In particular, pool mining on http://burstpool.ddns.net/ with 'Burst Mining System'?
That being said, what is the best way to track that my shares are properly getting submitted to the pool and such?
I like BURST and I have several different miners hitting it. But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out. There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!
Thanks all!
That being said, what is the best way to track that my shares are properly getting submitted to the pool and such?
I like BURST and I have several different miners hitting it. But before this coin becomes truly mainstream, honestly, everything needs to be easier to set up/sort out. There is quite a bit of info out there about it and I definitely appreciate all those who have contributed....but damn, ya gotta work for that info!
Thanks all!
No, remove passphrase for pool mining.
Ok, that's what I thought/said above. Thank you!
September 27, 2014, 12:30:21 AM
Hello, and attention all miners of burstpool.ddns.net
Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.
NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.
--Irotniga
Please remember that those who were mining before this announcement https://burstforum.com/index.php?threads/the-big-announcement.149/ get first choice for shares. In a few days we will be making them available to all, so please send your 1k (or less) burst to BURST-T7BK-USTG-KVKC-D2RDL and you will be sent 10 shares in the pool.
NOTE: Max 10 shares per person mining on the pool pre-announcement. Also, currently only available to those who were mining on the pool pre-announcement. If you are interested and weren't mining on the pool pre-announcement, place a bid order and wish that someone who was mining pre-announcement sells to you, or just wait till we make shares public.
--Irotniga
I got in on this earlier today. Yea buddy!
Jump to: