 eingeloggt? die meißte Zeit verbringe ich als "Besucher" im Forum. Ich möchte gar nicht erinnert werden, wieviel Zeit ich schon ver schwendet habe. Damals (TM) konnte man noch sehen welcher User sich wo Hauptsächlich Aufhält, diese Funktion geht aber leider seid geraumer Zeit nicht mehr.
|
|
|
|
|
Eine 51% Attacke ist wie qwk schon schrieb höchst unwahrscheinlich.
Was aber Realität werden könnte (bzw. schon mal versucht wurde*) ist das
man einzelne Transaktionen einfach nicht bestätigt, bzw. in einem Block aufnimmt.
Da sich die größte Hashleistung sowieso bereits in China befindet, wäre es ein leichtes
für die Regierung, die Mining Firmen dazu zu zwingen gewisse Transaktionen zu Blockieren.
Die Transaktionen müßten dann von einem Miner außerhalb Chinas in einen Block aufgenommen und
von 100 weiteren Außerhalb Chinas Bestätigt werden.
Das würde selbst heute eine gefühlte Ewigkeit dauern.
* vor Jahren hat ein Streit dazu geführt das Blöcke/Transaktionen vom Kanopool nicht vom Antpool Aufgenommen/bestätigt wurden.
Daraufhin haben -ck und Kano ihre Pool Software geändert und ihre eigenen Transaktionen zwingend in den nächsten von ihrem Pool gefundenen Block aufgenommen. Würde das heute passieren wäre das eine Katastrophe!
|
|
|
|
Wenn Bitcointalk weiterhin jegliche Innovativität außer acht lässt, wird das öfter passieren: Die Seite Coinpages listet das Coinform (nicht den Bitcointalk) als größtes und bekanntestes deutschsprachiges Bitcoin Forum zum Thema Bitcoin und Kryptowährungen: Coinforum ist das größte und bekannteste deutschsprachige Bitcoin Forum zum Thema Bitcoin und Kryptowährungen. https://coinpages.io/listings/coinforum/Sehr schade für den Bitcointalk und ich sehe wenig Optimismus, dass sich daran etwas ändert... Und was macht Coinpages zu einer wichtigen Referenz? Unsre altbacken Erscheinung hier schreckt einfach sehr viele Leute von vornherein schon ab. Als Neuling glaubt man anfangs garnicht, dass sich hier noch Leute tummeln... ging zumindest mir anfangs so  Ich finde das Design ok, aber ich nutze es auch nicht auf einem Handy. Und das hier Leben ist habe ich sofort bemerkt, aber das ist ja auch Ewigkeiten her. |
|
|
|
Don't bother posting any more pings, you're purposefully biasing the results.
I don't biasing any result. And I don't know why I should. This was the result from home vs. beeing logged into the server on the decix and do the same test. You can clearly see that the connection to your Amsterdam Node is ultra fast. Amsterdam is directly peered with Frankfurt, you can see that using mtr. It was not posted to make the passthrough look better, it was posted to show my situation from home. My home provider do not use the shortest way possible, for price I guess, peering cost money. I noticed that during the test. Actually that's not the second, there have been more. I don't get what you want to say, that was the second block found by my miner during the test. But anyway, it's not using the -N pasthru which is the whole point of using passthu so that your shares are validated and submitted as a block.
That's the point, I will test that and report the result I found. If the software fails, I won't use it as I don't want to put people on risk. i.e. if you set it up as you should, and not ignore the major advantage of using a block submitting node, you'd be better off by amost 100ms ... if your ping values were correct.
I ignore nothing, I simply did a passthrough in proxy mode with all disadvantage it brings with it. And yes, setting it up as Node is much better and you point me to that, thank you. |
|
|
|
You ping the node closest to you - there's a bunch of them listed on the home page: https://kano.isFrom your post I'd guess it would be nl.kano.is It's two servers with two different providers, so you may get slightly different results each time you try. And yes it submits blocks directly to the bitcoin network from there when your share gets to the node. done that: nl.kano.is from home
at worst
64 bytes from 45.76.32.61.vultr.com (45.76.32.61): icmp_seq=17 ttl=56 time=95.7 ms
at best
64 bytes from 45.76.32.61.vultr.com (45.76.32.61): icmp_seq=25 ttl=56 time=35.4 ms
nl.kano.is from decix
64 bytes from 45.76.32.61.vultr.com (45.76.32.61): icmp_req=15 ttl=56 time=7.96 ms (only 7 hops! in total)
from home 35.4 ms - 95.7 ms over decix 27 ms + 7,69 ms = 34,69ms not to bad from home, but more reliable and constant over the decix. And a second block was found: 1891851 Version 0x20800000 https://tbtc.bitaps.com/1891851When 10 blocks are reached I try the -N passthrough, but with my 3 TH it will take a while. |
|
|
|
Hmm - then that defeats the purpose of using a passthru though.
Your passthru is also adding latency to any blocks found - which can be noticeable if the passthru is far from the pool.
Yes, it may add an extra delay, but that passthrough is intend to enable people to connect to the pool that otherwise would not be able to connect due to the restriction of the american provider. For example if I use my home internet connection it is faster to connect over the passthrough. Ping time from home to pool 127 ms Ping time from home via passthrough 86,4 ms + 27 ms = 113,4 ms from passthrough (DECIX) to solo4.ckpool.org
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_req=6 ttl=53 time=86.4 ms
from my Home to solo4.ckpool.org
64 bytes from solo4.ckpool.org (51.81.56.15): icmp_seq=6 ttl=53 time=127 ms
from Home to passthrough
64 bytes from v38928.1blu.de (178.254.35.104): icmp_seq=3 ttl=56 time=27.0 ms so It depends on your specific internet connection. When you use -N it submits the block to the bitcoin network locally, at the passthru node, as soon as the share gets to the node.
(though the code has the mask wrong)
when I finished testing the -P passthrough, I will also test the -N and report the result, as this would be the better choice if that works ok. Edit: I was a bit shocked that my home internet is that bad, so I tested kano.is as well: home to kano.is
64 bytes from 45.77.7.149.vultr.com (45.77.7.149): icmp_seq=2 ttl=57 time=188 ms
home to decix
64 bytes from v38928.1blu.de (178.254.35.104): icmp_seq=3 ttl=56 time=27.0 ms
decix to kano.is
64 bytes from 45.77.7.149.vultr.com (45.77.7.149): icmp_req=1 ttl=57 time=148 ms total via decix:27 ms + 148ms = 175ms direct 188 ms the result is the same, over the decix it is faster. (using mtr displays the cause, my home provider routes using more hops) |
|
|
|
The passthru also is supposed to submit blocks itself, is that how you have it setup?
No, I used the -P switch, there is a bitcoind present but I did not try -N Well as he stated in the ckpool thread - he doesn't test it ... so how does he know it works?
that was in 2018, I am not the person who can answer you that question. But you are right by pushing me to test it, if I offer that service, and I take that very seriously. That's not an AB block - it's block version is 0x20000000
Well, yes, my fault, I was just reporting after it found the block without checking the version. |
|
|
|
Dann kann der Sonntag ja kommen (und der Hardfork beim Shitcoin). Mal sehen wie es dann weitergeht mit unserem geliebten Kurs der BTC. |
|
|
|
Due to a comment about the passthrough function of ckpool, I will Inform you that I stop this service now for a while until I have fully tested the proper function. Therefor I will use my S9 and my local testnet and ckpool as well as the used passthrough server to find out if there are any issue with it in conjunction with using AB. As soon as I know what the results are, I let you know if I can continue that service or not. Update: My test run a couple of hours now, and it found the first block using the latest source of ckpool from bitbucket. The miner (S9 with AB) is connected over a second instance of ckpool in passthrough mode. Proof: https://tbtc.bitaps.com/1891742I will let that run for a few days, and if that runs flowlessly I would consider that safe to go back online. I keep you informed. |
|
|
|
HOWEVER I'm not sure why -ck hasn't told you to shut down your solo passthru you run on his pool. The code isn't supported (I've had to fix bugs in it) and it DOESN'T handle AB blocks properly. You don't have to believe me, read what he said here: https://bitcointalk.org/index.php?topic=790323.msg43911218#msg43911218 ... and my follow up about some bugs in the code you are using: https://bitcointalk.org/index.php?topic=790323.msg44101418#msg44101418He's never put an AB block test through the passthru code, otherwise he'd see it doesn't work. That's how I found the bug, back when I was testing it properly, BEFORE I implemented AB on KanoPool. You posted a lot in that thread also. Any special reason why you ignored my post and are getting people to mine through that buggy code you are running? Thank you for dipping my nose on it. I was not aware of that, 2018 I was not looking after the passthrough function of ckpool. I use the latest version from cks repository and we talked about using it on irc, I had no trouble with it so far, and I did not get a negative response from eigther ck or the user. To not putting someone on risk, I will now remove the passthrough and test with my S9 and a local testnet. As soon as I know what the results are, I let you know. So again thanks for your warning. EDIT: My test run a couple of hours now, and it found the first block using the latest source of ckpool from bitbucket. The miner (S9 with AB) is connected over a second instance of ckpool in passthrough mode. Proof: https://tbtc.bitaps.com/1891742I will let that run for a few days, and if that runs flowlessly I would consider that safe to go back online. I keep you informed. |
|
|
|
|
Welchen sinn soll es haben ein Wallet mit TOR zu erstellen und dann per Paypal oder Kreditkarte
bei einer Börse (mit KYC) btc darauf Einzuzahlen???
Den TOR kannst du dir somit also schenken.
|
|
|
|
Kano's Solo is now live and working perfectly. I've said 'you're fired!' to the -ck solo.
Main restriction is that you MUST either use OEM firmware or BoS (Braiins). Aside from BoS miners using all 3rd party firmware are automajikly disconnected because of GPL license violation. While there has yet to be any verifiable proof that BoS finds blocks, being allowed only on solo presents zero risk to the main pool. Adder to that - IF someone using Bos does find a solo block then BoS will also be allowed on the main PPLNS pool.
For those wanting to use it:
1. Register to create new account & verify - you cannot directly mine to just a BTC address
2. Use a new payout address
3. Select Solo
4. Only then point the solo miners @ the pool & fire them up
Key points are that it must be a new account and the payout address cannot have been used before with Kanopool. Very nice to finally have a solo that is ran by someone who knows how to correctly code and more importantly - TESTS their code along with logging everything that goes on...
Well, that is nice to hear, but until the Kano solo pool did not find the first block, I would not say "it is working perfect". I would wait for at minimum the first block is mined. Anyway, I wish all good luck on mining. |
|
|
|
rfpool.org:3334 is connected to solo.ckpool.org:3333 (ckpool in Passthrough mode)
Just to double-check, stratum+tcp://rfpool.org:3333 still works and does the same thing that stratum+tcp://rfpool.org:3334 does, true? No, Port 3333 is not connected to anything to prevent people to mine unwanted to other instances of ckpool running on the same machine (one on Mainnet and one on Testnet). The passthrough to solo.ckpool.org only works on rfpool.org:3334. |
|
|
|
Heute ist mal wieder so ein Tag, an dem ich mich mit Popcorn und einem Bier vor den Chart setzen und einfach zuschauen könnte.  Wie oft habt ihr heute schon so den Kurs gecheckt? hm, also Angefangen mit schauen habe ich nach meinem ersten Bitcoin, der war damals bei ca. 50€ und bei 174€ habe ich nachgekauft. Edit: Funfact: der Wert meiner Bitcoins ist das mehrfache, meiner Lebensversicherungen mit Laufzeiten von 20-35 Jahren Einzahlen, die älteste wird nächstes Jahr Ausgezahlt. Und das in 8 Jahren. |
|
|
|
Da wird der Trusty von MtGox wohl nur noch ein wenig warten, bis er die restlichen Coins versilbert. |
|
|
|
My bad, I didn't know that port 3334 works on rfpool.org, you are right about this not being the best way to hide your mining activities from the government, but this pool could be used to by-pass US sanctions on other countries rather than the other way around, I found out about this when someone from Iran posted here about not being able to connect to Cksolo, and then I teamviewed into his PC to double-check if he got everything correct and it turns out that the the pool server "located in the U.S" is blocking him, so o_solo_miner gave me his pool URL to test it and it worked for him. To clear that a bit for future user, rfpool.org:3334 is connected to solo.ckpool.org:3333 (ckpool in Passthrough mode) The server is based on the decix in Frankfurt (Germany) and got a good speed to connect to the solo.ckpool. Main purpose is to enable a unrestricted access to solo.ckpool to the miner. The use is free as long as I am able to pay this thing. The use is at your own risk. to connect: pool => stratum+tcp://rfpool.org:3334 user => your_btc_address password => x you can see your stats as usual under https://solo.ckpool.org/users/your_btc_addressHappy Mining |
|
|
|
Wenn das wirklich so ist
und man die Betrüger damit auch noch unterstützt, sollte man die entsprechenden Threads schließen und diejenigen verbannen. Bevor noch weitere diese Gutscheine kaufen und dann in die Falle tappen.
Ob es so ist weiß keiner. Es gibt alle Nase lang "Verdächtige" Suche/Biete Posts, die Forumsregeln sind hier Maßgeblich. Moralisch flexibele Angebote wie IP TV usw. bleiben entsprechend der Forumsregeln ja auch stehen. Nachweißliche Betrugsversuche werden gesperrt bzw. gelöscht (z.B. Yesminer). Ein Mod ist nicht die Polizei und ersetzt auch nicht das selber Denken. |
|
|
|
Selbst wenn es den Server gibt, ist doch die Frage warum nimmt er so einen hohen Abschlag und Arbeit in Kauf?
Es würde ja viele andere Zahlungsmittel geben die sicherer und billiger sind und dabei weniger Arbeit bedeuten.
aber dann sieht es doch die Steuer. So oder so, nicht ganz Hasenrein die Sache. |
|
|
|
sehr Schade, dann warte ich halt bis der NDR ihn zeigt.
Gute Idee. Werde ich auch so machen Warten darauf bis meine GEZ-Gebühren einmal vernünftig investiert werden. Man hat ja sonst nicht viel davon. Weil du speziell den NDR erwähnst: Einfach nur so oder hast du Infos dass der Film da demnächst gezeigt werden soll? Im Vorspann der Promos sowie im Abspann war der NDR als Filmförderer Erwähnt. Ich denke das dann auch eine Ausstrahlung zu einem späteren (manchmal auch Einmalig vorher) Zeitpunkt erfolgen wird. |
|
|
|
Ich habe mich schon gefreut das man den Film auch mit Bitcoin bezahlen kann. Unter "Buy Film from us" wird er mit 0,0007 BTC Aufgeführt. (Quelle: https://gumroad.com/l/CryptopiaFilm) Im weiteren Verlauf des Texte jedoch dieses: This system is denominated in Australian Dollars.
For reference the rental price is A$8.99 = 5.88USD = 5.40EUR = 4.70GBP = 0.0007 BTC.
This system does not accept crypto at the moment. sehr Schade, dann warte ich halt bis der NDR ihn zeigt. |
|
|
|
|
Show Posts
