the fork detection is normal and wanted, nothing to worry about.
You have peers, good !
What is the block height and are you solo mining against this wallet ?
If you're using the mariadb backend, just keep popping off a few thousand blocks.
Do you have peers in your config and peers connected ? Is there anything in the brs.log ? There must either be a shortage of peers or an error message. Give it time, at least 30 mins I'd say, before looking for clues.
Emptying the complete chain is simple, just drop the database and run the init script (assuming you created the default database name) :
$ echo "DROP DATABASE burstwallet;" | mysql -uroot $ echo "CREATE DATABASE burstwallet;" | mysql -uroot $ mysql -uroot burstwallet < init-mysql.sql
I used the h2 backend only up to 1.2.9 and have no idea if the 2.0.x versions still use the subdirectory
for it. If so, just stop the wallet java process. Remove the subdirectory, start the wallet. Directory and database will be created, I guess.
@rds that might be different in a different legislation.
In my country, it is not yet clear on what value taxation is based on;
As long as you bought and sold coins, it is easy - if the timeframe was <1 year, taxation applies (both gains and losses, so you can reduce your taxes by losses in trading).
When mining a coin, the situation is not so clear, as I have received different info from my tax consultant and the press:
The fiat value of the minted coin at the point in time it was minted OR the fiat value when actually exchanging to fiat. And as the is no direct Burst-Fiat pair, does the double or triple exchange (Burst-BTC-USD-EUR) neccessary fall under speculation taxation, as you usually need several days for completing a larger transaction.
And finally, in my country everything you do might be regarded as a commercial activity (inducing further taxation). That is decided on case-by-case by a judge, if you have the money to take your case to financial court.
Whenever I run an application that is updating a blockchain, like BTC wallet or BCX wallet or ETN wallet, the Blago miner network connection slowly degrades to 0%. As soon as I shut down the offending blockchain app, the miner connection returns to 100%. This happens on at least 2 of my 3 machines, one's a Ltop and one's a server. Any thoughts on why this is happening?
Are these machines behind a NAT Router AND is it a cheap taiwanese plastic box ?
Usually, these cheap boxes run an ancient linux with dumb defaults to conserve memory, leading to connection losses if you have more than a few hundred connections open.
Remedy would be a "real" Router for IPv4 NAT or switching to IPv6. You could try out the free pfSense on a bare low spec box with two interfaces, depending on your connection and interface (modem).
for now if you're soling, use 1.3.6cg. Do not use 2.0.4.
well, I posted the 2.0.3 block-signing-error with log to discord, and shortly after 2.0.4 was released. I didn't notice the deprecation of 2.0.4 for solo mining.
Last block mined on 1.3.6 before moving to 2.0.4: 475585.
Since moving to 2.0.4 I did not win a single block in 22 days (350 TB should yield one every 3 days on average).
I pointed my miner to a 1.3.6 instance 3 days ago - and 2 blocks within 8 hours the same day (483736, 483850).
At the moment I don't have the time to compare my miner logs (deadlines) against the blockchain, so I wouldn't say this is a wallet issue although I "missed" 7 blocks.
@BurnMe Do you keep timestamped logs ?
but in the brs 2.0.0 this isn't working.
You might want to share any error log with us ?
@kalibc please check the Pool's reward address. You need to set your reward-recipient to that address exactly. Then, after a pool-defined settle time which is most often 4 blocks, your deadline submissions are accepted. Your current setting is for
2 TB disks, pre-plotted in 4 business days (Europe) for 35 € incl. shipping.
drive types are:
They work on SAS2 backplanes or SATA3 HBAs without issues .
No info on SATA Port multipliers.
smartctl output on request.
Also checking the specs of my mobo it is SATA II, it wont affect the speed if I connect SATA III disks?
SATA-2 has a (theoretical) throughput of 300 MB/s, 11 times what your system does per thread/disk; 27 MB/s.
You may chuck the bare HDDs from their USB enclosures (voiding warranty).
If there is anyone interested: have ~ 100 used internal SATA drives of 2 TB ea.
I could supply them pre-plotted in 4 business days (Europe) for 35 € incl. shipping.
Filesystem and -Parameters to your liking (Windows: NTFS, Mac, Linux and *BSD: whatever).
I just need your ID, choice of start-nonce, filesize, and filesystem type.
And 4 days later you have a fully plotted and optimized 2 TB Hard Drive in the mail !
Hm, I think this takes the fun out of it. I enjoyed the ahhh-lets-try-it-this-way-cycles tremendously.