 Show Posts
|
|
Pages: [1]
|
|
Let me tell you about my experience with the new wallet, maybe somebody can benefit from this informations.
Since about a year I do solo mining with my ~30TB HDD space. In version 1.2.3 no significant problems occurred.
When I updated my wallet, I saw that it runs into several forks. After a few times resetting the wallet I decided to delete the blockchain and build it up from scratch. (The blockchain file has a new name, old: burst.h2.db, new: burst.mv.db, don't know the background for this)
(a hint for the devs, because of the threading my PC was fully busy with burst and all other apps hang, maybe there is potential)
I have a different HDD for the wallet, but at this point I saw that when a block is found the drive of the wallet is realy bussy, even so long that the miner prints timeouts when submitting a deadline. (but raising the timeout isn't the solution because a fast miner hasn't an effect when the wallet is slow - I think)
In this threat I saw that there are more users that have problems with forks.
I moved the whole wallet to my SSD and changed these settings in the wallet: nxt.maxNumberOfConnectedPublicPeers=50 (dft. 20), nxt.sendToPeersLimit=25 (dft. 10).
Since then (about one week) my wallet never again run into a fork. As bevore I find about 1 block a day.
I don't know which change was the decisive, but when I look into my wallet it says 42 connected Peers (including all major pool e.g. burst.ninja, pool.burstcoin.it, pool.burst-team.us, pool.burstcoin.eu, ...) and 45MB DL to 1GB UL in 18 hours, so I think this changes are good for the Burst-Network.
|
|
|
|
I'm running quite a few Seagate 4 and 5 TB external drives, been running quite a while without issue. I bought them because the price was right  . As far as I can tell BURST has done zero damage to them. Everything is still running exactly the way it should be. I bought recently four 8TB HDD of Segate. One was broken directly, one has displayed an error after about four weeks in RAID. Two and a exchanged run until now well so far. The super cheap "archive" drives must be used with some care. I have found that if you throw too much data at them too fast, then they totally freeze up, sometimes crashing windows 10 along with themselves. They can go silent and not show up in disk manager for hours if they first get stressed out. Not sure if it is thermal or cache/firmware issues or both. in any way, if i don't push data to them too hard ( no copy these 4TB plots onto this 8TB drive kinda operations ) then they work just fine.. i use the free program FastCopy to copy stuff in a slow pace onto the drives ( fastcopy can be set up to run at reduced speed, i use 50% setting) when an archive drive has been stressed to become unstable, even reading from it is a bitch, it cannot sustain any kind of reasonable transfer rate.. but if you keep it on for some hours or longer, it tend to sort itself out again. Also filling the drive up completely seems to make it go berserk. Haven't tried to have burst plots on archive drives, but i guess it will be allright perhaps as long as you leave some room on the drive to make the firmware happy. Don't copy your plots over at full speed though, they choke on 100 mb/s for more than 20-40GB at a time. If you copy slowly ( using fastcopy or similar ) you can copy hundreds of MB wo issues With small chunks of data ( 5-10 MB ) you can copy as fast as the SATA allows you to, they are fine with that. As I understand it, they use part of the platters for intermediate storage, and as long as you don't fill that up, they are pretty fast. It was the archive one. But the first drive was broken on first connection, so there wasn't a fault on my side. The second drive was broken after a short power cut (but there wasn't any writeoperation active at this moment). I never hab problems while writing to this disks, as long as you consider that these hard drives, because of the technology, are a bit slower at writing than conventional drives. |
|
|
|
I'm running quite a few Seagate 4 and 5 TB external drives, been running quite a while without issue. I bought them because the price was right . As far as I can tell BURST has done zero damage to them. Everything is still running exactly the way it should be. I bought recently four 8TB HDD of Segate. One was broken directly, one has displayed an error after about four weeks in RAID. Two and a exchanged run until now well so far. |
|
|
|
C`mon guys i cant believe nobody added this coin yet to Yobit: https://yobit.net/en/addcoin/Guys add the coin to yobit so that I can buy some. I`m waiting here for like 1 month to buy some. but i cant understand one thing here, why if you want to buy burst, you don't use one of the current exchanges where we are? Because I dont want to have like 1000 exchange accounts. I am usng Yobit and i would like to buy some BURST ffs. Please guys add it to yobit, i see you guys need some investors, man there are tons of traders there who would pump the price up to 100 satoshi!!! Just add it to Yobit and all problems will be solved!! Lol c`mon guys, is it so fucking hard to just add it to Yobit, it would help your currency. It takes 5 minutes to fill out the form. Seriously WTF guys, please dont be lazy!  And why can't you spend those damn 5 min.? Laziness...? No because i have no idea of this coin, you have to fill out some tech specifications there, and i have no clue about this coin whatsoever. It is the devs that are lazy, this coin needs to be on all exchanges, including where I trade usually at Yobit. So please somebody add it! I think we can help you better, if you ask the tech details you need to know to add it. But I dont think it is as easy as you imagine, because I checked the form to add new coins. BURST isn't a POW or POS coin, its a POC Coin, so the standard form doesn't help for this coin. |
|
|
|
Are we going to "save" the coin, or to destroy it?
I do not see anything criminal to show that the network is voluntary. Criminal would be if he would steal out of your wallet. BinLaden said several times, that the network can be attacked, not necessary by him. However, if you tease him to proof it, he might accept this invitation. THEN you will have to wait a few days till he allows transactions. He also said what we need to do to avoid a possible attack, ...
I feel I have to point out that there is no law that says 51% attacking a cryptocoin is a criminal act. That's like print counterfeit money, I do not think this is legal in most countries of the world. |
|
|
|
|
