|
Juckt das eigtl. überhaupt noch wen? 0.03 BTC pro Woche ist doch tot.
|
|
|
|
|
Na klar rechnet sich das nicht.
Paid out in last 7 days: 0.11 BTC
Das Ding ist einfach nur tot. Lasst es in Würde verrecken.
|
|
|
|
|
Was hat es eigtl. damit auf sich, seine Passphrase auf irgendwelchen Seiten im Internet einzugeben? Ist das nicht... schlecht?
|
|
|
|
|
How is the personal claim method - the one that needs a Facebook account - not a giant scam to create a giant database of Facebook<->BTCaddress associations?
|
|
|
|
|
Wenn der Download und die Peers von demselben Typen empfohlen werden, ist dann nicht beides schlecht? Wenn die Chain, die ich aus den Peers kriege, auch Mist ist, was bringts dann? Andernfalls, wie kann der Download Mist sein, wenn er auch die Peers empfiehlt?
|
|
|
|
|
Wenn ich im Moment bei einem Pool mine, der mir unter 1PB diff anzeigt, was genau mache ich da? Füttere ich einen (bösen?) Fork? Helfe ich der "echten" Chain? Ist das alles umsonst? Mir fehlt ein bisschen das "Mach dies und das, das ist das beste im Moment".
|
|
|
|
|
Also macht man nichts falsch, wenn man versucht, das offizielle Wallet am Laufen zu halten? Oder was kann man jetzt am besten tun?
|
|
|
|
|
And again, NOTHING works. My pool is down, other pools are down. The main site is down. It looks like the whole ecosystem is running in the basement of one amateur. Everything is constantly down.
|
|
|
|
https://forums.burst-team.us/topic/7393/pools-being-robbedThese guys don't even have their social structure under control. WTF. You can only guess who is telling the truth because the pool page doesn't show any announcements and generally looks like a half-baked piece of shit. No TLS either. BURST is so rotten.
|
|
|
|
|
The whole Burstcoin ecosystem looks like a steaming pile of garbage. None of these crappy sites have heard of TLS, my pool (pool.burstcoin.eu) just randomly(?) changed its assignment address. No pool is without constant connection errors. The "official" blockchain explorer doesn't know anything about a transaction that my wallet shows me etc.
Is this shit even alive? It looks like it's running on autopilot with no one giving a shit really.
|
|
|
|
Hi, grade was bestellt und bezahlt. Lieferung lässt noch auf sich warten. Wäre aber schön, wenn ich heute noch...  Thx |
|
|
|
|
And again it's down, same DNSSEC problem.
Guys, if you don't know how to handle your servers, hire someone who can. This is embarassing.
|
|
|
|
It appears that you have a an advert blocking browser extension enabled.
Our Publishers use this revenue in order to monetize their websites and provide you with their content. To permanently remove this message please consider to white list our website. Blablabla... probably clickbait bullshit. Edit: Issue seems to be fixed. |
|
|
|
Of course, if you don't use a DNSSEC-capable resolver, you don't notice any problem. You also don't know if the results are legit. The problem is that DNSSEC has been deployed once by btcclicks.com, but is not being maintained properly. That is worse than not having DNSSEC at all. Hopefully you must be facing any corrupted cache or cookie problem. Clearing all your browser history might help you better. If you look for instant solution, just chance your browser, this might make you access btcclicks in seconds.
Please, if you have no idea what this is about, don't post. We are way below browser level here. Type in cmd.exe nslookup btcclicks.com 8.8.8.8 and see that it's broken. http://dnsviz.net/d/btcclicks.com/dnssec/ and see that it's broken. |
|
|
|
|
btcclicks.com DNSSEC is broken.
|
|
|
|
Currently, Bitcoin Core uses an algorithm to monitor the network and see how long transactions take to confirm and then uses that to determine what fee is needed to get a transaction to confirm quickly. If it doesn't have sufficient information since it had just been started, it could be miscalculating.
Since syncing takes quite a long time, depending on the last sync upto half an hour, is that included in the fee determination or do I have to let it sync and _then_ let it determine the fee on top of that? If you have the tx id, that might be helpful ;-) I have but I don't want to create data points. |
|
|
|
|
Yes, Core 0.11.2. I start it on and off when I need to do something with my wallet. Usually it catches up several days and then I do a transaction. This particular transaction was sent with 0.00013 BTC fee which seems reasonable?
Edit: 0.000013 BTC fee, not 0.00013.
|
|
|
|
|
Hi,
I sent a transaction using 0.11.2 and the recommended fee for "normal" confirmation time over 6 hours ago and it's still unconfirmed.
Has the default fee become too low somehow?
Cheers
|
|
|
|
|
Well, not anymore.
In other places, people didn't even know there was a leak until I asked them why my unique address was spammed. For example, one forum installed Tapatalk and found out this way that the plugin transferred the complete user database to Tapatalk. It was only when Tapatalk screwed up and spammed all addresses with a Beta notification that this was discovered.
People always assume that mail adresses getting spammed is just a fact of life. If you follow the leads a bit, you can see exactly where the leaks are. And if you disable leaked addresses and generate new ones, spam doesn't even reach you en masse.
|
|
|
|
|
Can't get more off topic. Someone close this cesspool of a thread.
|
|
|
|
|
Show Posts
