Looking at https://web.archive.org/web/20220207120417/https://braiins.com/os/plus/license the license page was there as of 7 Feb 2022 so between then and when you forced an archive back in July it changed. Could have been 2 minutes before you clicked on it or it could have been 2 minutes after the last archiving. Unless someone else archived it someplace else we can't know. As for the percentages / hash rate some people feel the power savings and speed improvements that *they* see is worth it. As always YMMV. Some people have discussed good speed improvements and much lower power use. Others, like you have seen very little or none. If you have hardware that can be pushed harder at a lower voltage you will probably benefit more then someone putting it on an old & abused miner that can't do much more. -Dave |
|
|
|
|
Looks like a bunch of bad hasboards. If you look you are getting found 0 ASIC messages or found 30 AISC messages.
Did this just start or has it been slowly dying (getting slower as it shuts off boards)
Pull the boards and see if there is any obvious damage, and check the cables and such.
The T17 units were not the best when new, now going on a couple of years old there seem to be more of them dropping.
At least from the posts that are popping up.
-Dave
|
|
|
|
So, the card itself is issued though webbank took a look and although it's not really highlighted on the Gemini site it is on the webbank site: https://www.webbank.com/brand-partnersI have really just been treating it as a card that has 3% rewards on restaurants. Which at the moment is less then the 5% discover card but there are still places that don't take discover (looking at you uber eats) so it has been getting some use. Not a fan of the interface on the gemini site for card activity / billing but it's not the worst I have seen. -Dave |
|
|
|
|
Get well soon. The 1st few days are rough, but after that so long as you plan your movements it's not bad. And as I said, Mr. Ice Pack is your friend.
Don't try to tough it out without the pain meds. I didn't 'need' them but it did make some things just easier to do.
-Dave
|
|
|
|
Very cool. Wonder what will happen over the years with all the exhibits out there of BTC stuff. Things like this, the mining museum and so on. Will they pop up all over or stay as little specialized exhibits. And for humor since it's the British Museum:  |
|
|
|
May I ask what the purpose is to use "your" base57 encoding of public addresses (omitting "z" from allowed characters)?
I'm just trying to find a faster way to generate only addresses with some characters but avoiding vanitygen and modifying the base58 for the address while keeping the base58 for the private key I guess the question is why? Vanitygen and others work well enough and you can from there just eliminate the addresses that have characters you don't want. You could easily even automate the process for 1000s of addresses per hours with even a low power CPU. -Dave |
|
|
|
Tor can actually make things more risky. Some of the guides for using Tor with Electrum set it up in such a way that you are only connecting to a single server in order to maximize privacy. This obviously means you are downloading the block headers and all your wallet information from only a single source, which increases the risks of being fed incorrect or malicious information.
Do keep in mind this holds true if the one Tor server you're connecting to is not yours. When I connect to my own Electrum node through Tor, I do connect to a single Electrum server, but there is no risk of getting malicious information.
As for the yet unanswered question about electrs default logfile location; electrs doesn't create a logfile by default. It uses Rust's built-in env_logger, which supports log levels from 'ERROR' (very serious errors) to 'TRACE' (extremely verbose) - all the log levels are declared in Rust's enum.Level. There's also a table in electrs' GitHub with pretty much the same information. By default, env_logger writes everything to stderr. But keep in mind it's a trivial task piping stderr to a file. In my little experiment with log level DEBUG, I could not see the IP or Tor address I was connecting from and in the code it doesn't seem that it's logged, either. But it's simple to add, as others mentioned. I do see the queried addresses, though. If you run electrs with log_filter = DEBUG and grep stderr for DEBUG electrs::server] 0:, you will get the communication between your SPV wallet and your Electrum server. bitcoin@localhost:~/electrs> /home/bitcoin/electrs/target/release/electrs 2> >(grep 'DEBUG electrs::server] 0:')
[~snip~ DEBUG electrs::server] 0: connected
[~snip~ DEBUG electrs::server] 0: recv {"jsonrpc":"2.0","method":"server.version","params":["Sparrow","1.4"],"id":1}
[~snip~ DEBUG electrs::server] 0: send {"id":1,"jsonrpc":"2.0","result":["electrs/0.9.8","1.4"]}
[~snip~ DEBUG electrs::server] 0: recv {"jsonrpc":"2.0","method":"blockchain.headers.subscribe","params":[],"id":2}
[~snip~ DEBUG electrs::server] 0: send {"id":2,"jsonrpc":"2.0","result":{"height":747717,"hex":"00c00020c072fd1a50fe409f82942c9dfc46565761c38522589103000000000000000000d8c783dcd4e3eb05372ae116978d9fbd2d4fd1d29f3a3c6dfa4f841bb739ac623faee962042a0a17ae7fbf9d"}}
[~snip~ DEBUG electrs::server] 0: recv {"jsonrpc":"2.0","method":"server.banner","params":[],"id":3}
[~snip~ DEBUG electrs::server] 0: send {"id":3,"jsonrpc":"2.0","result":"Welcome to electrs 0.9.8 (Electrum Rust Server)!"}
[~snip~ DEBUG electrs::server] 0: recv [{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[1],"id":4},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[2],"id":5},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[3],"id":6},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[4],"id":7},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[5],"id":8},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[10],"id":9},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[25],"id":10},{"jsonrpc":"2.0","method":"blockchain.estimatefee","params":[50],"id":11}]
[~snip~ DEBUG electrs::server] 0: send [{"id":4,"jsonrpc":"2.0","result":0.00013},{"id":5,"jsonrpc":"2.0","result":0.00013},{"id":6,"jsonrpc":"2.0","result":0.00013},{"id":7,"jsonrpc":"2.0","result":0.00011838},{"id":8,"jsonrpc":"2.0","result":0.00010052},{"id":9,"jsonrpc":"2.0","result":0.00005394},{"id":10,"jsonrpc":"2.0","result":0.00001},{"id":11,"jsonrpc":"2.0","result":0.00001}]
[~snip~ DEBUG electrs::server] 0: recv {"jsonrpc":"2.0","method":"mempool.get_fee_histogram","params":[],"id":12}
[~snip~ DEBUG electrs::server] 0: send {"id":12,"jsonrpc":"2.0","result":[[1023,560],[511,1662],[255,12801],[127,12906],[63,59896],[31,195453],[15,1397569],[7,756035],[3,430544],[1,314814],[0,0]]}
[~snip~ DEBUG electrs::server] 0: recv {"jsonrpc":"2.0","method":"blockchain.relayfee","params":[],"id":13}
[~snip~ DEBUG electrs::server] 0: send {"id":13,"jsonrpc":"2.0","result":0.00001}
[~snip~ DEBUG electrs::server] 0: recv {"jsonrpc":"2.0","method":"server.ping","params":[],"id":14}
[~snip~ DEBUG electrs::server] 0: send {"id":14,"jsonrpc":"2.0","result":null}
[~snip~ DEBUG electrs::server] 0: recv [{"jsonrpc":"2.0","method":"blockchain.scripthash.subscribe","params":[~scripthash~],"id":16},{"jsonrpc":"2.0","method":"blockchain.scripthash.subscribe","params":[~scripthash~],"id":17}, ...]
[~snip~ DEBUG electrs::server] 0: send [{"id":16,"jsonrpc":"2.0","result":"~snip~"},{"id":17,"jsonrpc":"2.0","result":"~snip~"}, ...]
...
I obviously had to redact a lot; but in essence, the client (in this case, Sparrow - I noticed our esteemed forum member achow101 is mentioned as contributor!) queries the blockchain.scripthash.subscribe Electrum protocol method ( a list of all these methods). In this case, blockchain.scripthash refers to a 'hash of the binary bytes of the locking script, expressed as a hexadecimal string' [quote: https://electrumx.readthedocs.io/en/latest/protocol-basics.html#script-hashes]. So basically wherever I wrote ~scripthash~, there are script hashes, a different representation of the addresses of whoever's querying. Especially since they're bunched together in a small number of individual requests, we can say that electrs does link transactions together in its default logs. Makes you wonder how difficult it would be to recode some of the SPV wallets to never connect to the same server for more then one request before going to another random one and then going to another random one. You would have to keep a local log but it would make some analysis a bit more difficult. That or as others have said, run your own. As many of us have pointed out many times you can easily do it for under $100 in hardware. And with all the pre-packaged / pre-configured setups out there it is not that difficult for a novice to do. -Dave |
|
|
|
I find it quite disturbing that there hasn't been a single new BIP submitted to the github repository at https://github.com/bitcoin/bips, ever since 2021-06-27 [a bunch of BIPs about descriptors were made at that time]. What happened? It is not about now being submitted - there are BIPs not merged. There is quite huge list of pull requests: https://github.com/bitcoin/bips/pullsI do not know who is responsible for processing that requests, but indeed, it looks like a quite big backlog. The threshold to submit a PR is low, so some of them may not be seriously considered, and/or are a low priority. The development of Bitcoin is different from most other software because no one entity is responsible for it, and also because there is so much commerce that involves bitcoin. The later gives an incentive for many to try to influence the development of bitcoin for various reasons. As achow101 said above, much of the work regarding BIPs is done outside of github. Taking the part I bolded I will say that for a lot of projects now that is true. 10+ years ago it might have been different. But with so many other methods of real-time digital communication now being used by so many people (telegram / discord / etc.) that for a lot of the preliminary and even mid-term programing work it is easier to do it using those services then github. Bitcoin uses the bitcoin-dev mailing list, but I know of many (non crypto) projects that by the time it's on what we see as the github for the project it probably spent several months on the programmers private * git space while being discussed in 3 discord channels. -Dave * It's not private like you can't see it, it's private like if you don't know to look or ask where it is you probably will not see it. |
|
|
|
|
Or does he want out but knows that since he is the face of the company he has to slowly leave.
According to reports the man still has billions in fiat and a ton of BTC. Did he hit that 'enough' place in his mind and wants to do his own thing.
Although rare it does happen. And, as others have mentioned it could just be time for someone else at the helm.
In the end, both Saylor and Microstrategy will be just fine.
-Dave
|
|
|
|
|
For some people I guess the other part of the questions is where the BTC is going and what else is happening.
If it's in a wallet that I control then 1 conf for just about anything is good for me. Even if it's for 'real' amounts or property there have been so few orphans / reorgs that I can say it just does not matter.
Lets face it, if I was giving someone $1 million in cash for 42.5 BTC right now I would be more worried about a goon with a gun taking the cash then having someone take the BTC back through a reorg.
-Dave
|
|
|
|
|
Banks have to allow their cards to be used with Apple / Google / Samsung / etc. pay. Beyond that they can also dig into specific devices and model lines.
If you poke around you will see at times that people are complaining when they switch devices that the card that worked with their Samsung phone and watch no longer works with their Apple phone and watch.Or it's still the same phone but they got a new fitibt and it worked with the old one but not the new. Most of the time it's not a big deal, just take another card out of your wallet and use that one. Other times, like this when you want to use a specific card for a reason you are just out of luck.....
-Dave
|
|
|
|
|
No the import tariffs are be paid as the products enter the country. They are already in the price.
Now they have to charge sales tax too. The only good thing about it is that is a domestic ship so you should get it in a week at most.
However if difficulty and BTC price remain flat you are still a year out for paying off the cost of the miners even with free electric.
Still not a great deal.
-Dave
|
|
|
|
|
In addition to all above, they also did not move the coins enough and use other people (mules) to do it.
Not a lesson in crime here but if money goes from A to B to C to D to E before going back to A it's a more difficult to prove.
It also costs time and money.
-Dave
|
|
|
|
...
Is there a way to reload cards with more money somehow?
I heard they are planning to increase limits from $250 to $1000, so that is not bad news at all if it happens.
btw did you pay any fees for transactions and payments?
No to the reload and no to the fees. Outside of the original cost of getting them there have been no issues. I was using them to get some motorcycle parts from websites that were using a processor that I have had issues with before. But I bought $50 cards for purchases with shipping that came to a bit less. I just wanted the rest of the funds off the cards. Wound up adding them to my 7-11 app and got some overpriced snacks. -Dave |
|
|
|
See if sudo journalctl -n 10000 | grep electrs shows you anything. From what I saw with a quick read you can set the log level and location in the config but that should find it. Did you build from scratch or are you running a prepacked node setup? That may change the location / level and even availability of the logs. -Dave |
|
|
|
How long do the outages last and how much space do you have? There are many places now selling things like the Tesla powerwall. More for commercial / semi-commercial environments then for home use. In the end they are really just BIG battery backups but they are using old lithium car batteries so for the power they produce the cost is less then going out and buying a massive Schneider Electric unit https://www.se.com/ww/en/product-range/22545656-galaxy-vl/?parent-subcategory-id=8030#overviewThere are also solutions that just let you chain a large number of regular 12V car batteries together. Not as efficient and it takes up an insane amount of space but they do work. All depends on where you are and how much you want to spend and how much space you have and how much time you want to spend maintaining it. -Dave |
|
|
|
|
I don't know electrs or how it is setup out of the box, but electrumx does allow for a fair amount of logging.
With electrumx I can see your IP, what addresses you are checking and if you send a TX I again know your IP and have the information about the TX.
That is what people are talking about. It does not send that information anywhere but you as the server operator can still see it.
I *think* electrs does the same. But I never looked.
-Dave
|
|
|
|
Working it a bit backwards. Since you have the address that the BTC went to, you can see then address / addresses the BTC came from. Most major exchanges have known wallet addresses. If that address was funded from one of them you might be able to contact them and they can contact the person who the funds were sent to. It's a long shot but you never know. NOT LEGAL ADVICE but according to Wikipedia: In Victoria, the Victorian Crimes Act[9] defines this crime by exception "72.3(c) A person's appropriation of property belonging to another is not to be regarded as dishonest if he appropriates the property in the belief that the person to whom the property belongs cannot be discovered by taking reasonable steps.
If you can't trace the address and the police don't have a "paper wallet" listed as stolen or missing. Then it's probably yours. If you are worried you can always sit on the funds for a while before doing anything with them. -Dave |
|
|
|
|
Insurance.
Unless you are funding it all out of pocket interest on borrowed money.
Might be a small point but if there is a dip again in price you will want funds available to cover operations till the price rebounds. If you are living 'paycheck to paycheck' (block to block so to speak) and the price dips do you really want to sell on the dip because you have to pay bills.
Also remember unless you have an agreement in place you are loosing a certain percentage when converting to fiat.
Going to need a tax person and possibly a lawyer.
I'm sure there is more as you get bigger.
-Dave
|
|
|
|
|
Show Posts
