They are still here. Am I asking too much? I figured they would have moved by now. With the loaded XMR being worth more than $75 between the pair that are loaded I figure someone would have bought them.
Been concentrating on moving out more of the car stuff over the summer, so I have not been pushing the collectables but would have believed that someone would have taken then my now.
-Dave
I don't think it's too much. I just think more people are hodling right now since the price seems to be jumping and btc consolidation starts to grow a bit early... I'd take the loaded ones, but not sure if you are willing to split them. I already have a few non-loaded, so it feels counter-productive to me atm How about $200 and you take the non-loaded one too. Just cleaning up and don't want to have just the one sitting around. 3 do not take up any more space then 1. -Dave
|
|
|
Fan in the case sucks. I think it's #3 or #4 I had to replace so many of them. m.2 SATA only will not take an m.2 NVMe No SD card. No Drive. No power supply. No support. US shipping only. Payment address: bc1qdufcfvlqtuhed84qrs4lfrhfla2ryw6jzljezu If you have any questions ask. -Dave
|
|
|
Nah, it's not a big deal. 1) The issue is they were pushing Genesis and with this. The lawsuit alleges that Gemini knew Genesis’ loans were undersecured and at one point highly concentrated with one entity, Sam Bankman-Fried’s Alameda, but did not reveal this information to investors 2) They will probably settle pay a fine and move on. The biggest is going to be who pays what. Everybody involved with Genesis is getting hit with lawsuits. So this was not at all unexpected. Since they are NY based they make more headlines then some small offshore exchange.
#1 is what we are talking about now #2 is 100% user error sending a token that Gemini does not support to Gemini back in 2018 #3 is a 2 post user from back in 2019 about them closing their account. Legit CEX will close your account if anything looks the tiny bit off to their security people. And they will never tell you why. There are a lot of reasons not like Gemini / CEX. These are not any of them. -Dave
|
|
|
Or do both.
TOR for a bunch of connections to smaller hobby nodes and clearnet to the big public only ones.
You would give up some (OK a lot) of privacy, but you would have the option of how you want to route payments.
You can actually open to a clearnet from the TOR one, so you could just route all your payments through the TOR one and if needed it would use your clearnet for the next hop.
-Dave
|
|
|
As I have been saying for a while, if you follow any kind of financial advice from instagram, facebook, twitter, reddit, this forum. You are an idiot and deserve to loose all your money.
There is no vetting, there is no accounting, there is no proof. And now, it's gotten so bad that corporations have to step in to police their users since people are loosing money and their lawyers and the government are looking for easy targets to blame. So they are cutting off everyone. It's easier then dealing with it on a case by case basis.
-Dave
|
|
|
I might get jumped on for this but I really see it as an answer in search of a question.
1st you need people who care about privacy, and as we see time and time again, it's a small, but very vocal segment of the BTC community. If you really want privacy for your crypto transactions then use one of the privacy alts.
2nd you need a bit more powerful HW and more bandwidth with BIP 157/158 then with a regular non private SPV wallet. Nor a big deal, but still worth a mention.
3rd Just on a personal level I am getting REALLY tired with the perpetual it's too expensive to run a node BS. Yes in many parts of the world $125 is more money then a lot of people will ever be able to spend on one. These are not the people who care about privacy. For the most part, they want to quickest and simplest way to get a TX done. Privacy is way down on the list.
-Dave
|
|
|
mononautical on twitter sums it up nicely: https://twitter.com/mononautical/status/171573687153426481814) This attack isn't easy. Pulling it off involves: - opening two channels with the victim. - routing a payment through them. - successfully replacement-cycling the victim's htlc-timeouts for Δ blocks. - without the victim discovering the htlc-preimage transaction. I would still be more concerned with someone stealing one of the RaspberryPi nodes in a box on my desk and getting my BTC that way then pulling this off. It's just so out there as to be not something worth worrying about for the average user. For the larger businesses running nodes I could see it being a concern, BUT since as pointed out there are some ways, admittedly non optimal ways but still ways, of mitigating it, once again not that big a deal. -Dave
|
|
|
They are still here. Am I asking too much? I figured they would have moved by now. With the loaded XMR being worth more than $75 between the pair that are loaded I figure someone would have bought them.
Been concentrating on moving out more of the car stuff over the summer, so I have not been pushing the collectables but would have believed that someone would have taken then my now.
-Dave
|
|
|
<Bump>
Not even one reply. Am I asking too much? Even with the increase in the price of BTC it's still just about $150 shipped US.
-Dave
|
|
|
Then you come in one morning and close all the channels to nodes that are not yours at once. Why? You can just turn off your nodes. You don't have to close those channels. Let your users do that, so they will start betting, by closing their channels in panic, and setting higher and higher on-chain fees, and reaching levels, where a proper fee to get it included in the next block, will reach the holy "1000 satoshis per virtual byte" limit, or will exceed the amount locked in the channel. And then, your side would be clear. Being offline is less serious crime than closing the channels by yourself, even if the final outcome is exactly the same. It is sad, that LN can be attacked just by being offline, but it is true, and many attacks can be done in this way. Just flipping the power switch and making everyone else force close would probably cause a lot more disruption since your nodes are offline. And a ton of speculation as to what happened. Closing down the channels would show that you attacked it. In the end it does not matter, it would take a while for the LN to recover. Flipping the switch would also cost you since you get the force close penalty from the nodes that are not yours. Shrug, as I said. Not something to worry about. Could also do the same thing with mining in general. -Dave
|
|
|
I put this in the same pile as the Wormhole attack discussed here: https://bitcointalk.org/index.php?topic=5466886Yes it can be done, but the cost and effort are so high as to not be worth it. There are a lot of ways to attack BTC and the Lightning Network. Most of them are so esoteric / expensive / just about impossible to implement as to not be worth it. Want to destroy LN or at least set it back years and years? Heck I can do that for you for less then BTC20000 / $600 million USD As of now LN has about 5500 BTC in it. Just start spinning up nodes and connecting to other nodes and charge 0 fees. Just keep adding and adding and adding. People will connect to you, you connect to others and soon just about every lowest cost route is running thought you. There are people who have 10+ connections to other nodes but they are all yours. But you now have 45000 nodes which is 3x as many as there are now and those 20000 BTC are all in LN so you own control 75% of the LN. Probably take about a year and everyone would be amazed at it's growth. Then you come in one morning and close all the channels to nodes that are not yours at once. Insane high fees so they are all in the next hundred blocks. Then when you have time you close the channels between your nodes, sit back and watch the chaos. But, nobody has done it. So worrying about some other attack that requires some extreme programming and other things is not a real worry. -Dave
|
|
|
Eliminating all the other technical bits about this you then wind up with the issue of what happens when the file changes and words are removed. https://www.abc4.com/news/9-words-removed-from-the-dictionary/It's 10 years from now and one of your words was Brabble. And you go to recover your seed and it just does not work. Sucks to be you. Well worked on standards like BIP39 exist for a reason. This just makes a mess of it. As per the theoretical calculation time taken to brute force the 24-word recovery seed from the BIP list is longer than the age of our universe which is expected to be around 14 billion years. The universe is expected to last much longer then that. As in trillions of years. Our solar system will be toast in about 10 billion years. Either way does not matter. Still won't crack it in a lifetime. -Dave
|
|
|
zoo zoo zoo zoo zoo zoo zoo zoo zoo zoo zoo wrong
Also sounds like a kid in the back seat and the adult in the front.
... The chance of a 12 word seed having the same word at least twice : 3.18% (1 in 31) The chance of a 12 word seed having the same word at least three times: 0.0052% (1 in 19,128) The chance of a 12 word seed having the same word at least four times: 0.0000057% (1 in 17,407,725) The chance of a 24 word seed having the same word at least twice: 12.65% (1 in The chance of a 24 word seed having the same word at least three times: 0.048% (1 in 2,089) The chance of a 24 word seed having the same word at least four times: 0.00012% (1 in 814,729) ... Makes you wonder how many times people have hit that 1 in X thing and not even noticed. I know I have had at least 2 24 words with the same word twice that I was actually using for a while. But, I have also generated so many for testing that I did not secure since thy were just for tests that it could have had 3 or more of the same but I never even looked. -Dave
|
|
|
Good morning everyone,
@ o_e_l_e_o,
I appreciate your explanation and the breakdown of the quirks of the mempool / mining process. Also I didn't realize that the inbound and outbound connections were functionally identical but it makes sense when I think about it so thank you for that comment.
@ DaveF,
Yes my computer has more RAM than that but I'm running the blockchain on an external HD that's connected via USB 3.1. Also I believe that I am properly sending data to the bitcoin network behind the VPN as certain gateways for our VPN provider do allow for port forwarding which I've poked a hole in my router to open. In fact over the last 20 hours or so it appears that my node has sent over 5GB of data. At one point I had 37 inbound connections behind the VPN (now it's down to about 1/3 of that however).
Also just an FYI I did notice that the same issue with the block propagation delay to my node (behind the VPN) happened again as I waited for another transaction I sent shortly after I posted. This issue however seems to happen fairly regularly as this has happened several times over at least the last year or two I've been spot checking with both with my node in the clear and the one running behind the VPN connection. Regardless though everything seems to be synched up at this point. Either way I appreciate your feedback. Curious though, how did you know what my VPN provider was? I'm assuming you seen the IP and looked it up but how did you get the IP? Thanks.
Didn't (and don't) know who your provider is or what your IP is, but it's a common issue with a lot of VPNs. Public IP4 IPs are expensive. With the IP4 address space exhausted $35+ per IP is common. So it's not like they can just keep throwing new IPs into the mix. So blocks of IPs get blacklisted and then issues start to come up because even if they are doing a 1 < -> 1 IP for your VPN which most places don't, the last person on that IP could have been an ass and killed it's reputation. And as I said if it's a shared public IP like 90%+ of the providers then it's even worse. Since you don't know what other people on that IP are doing. -Dave
|
|
|
...I wonder what would cause such a propagation delay to my node? It is behind a VPN but it does have inbound connections as well....
Could be the VPN. Remember, most VPN endpoints are abused and their IPs do get blocked even if it's not your fault. I use the same VPN provider you do and have a malicious node, my node does not get blocked my IP does, which just so happens to be the same as yours. Your node shows a connection but it's really not sending anything. Have seen it now and then. Are you running on at least an SSD with 8gb ram and a processor that is less then 10 years old? Could also be hardware that can not keep up churning away on something. -Dave
|
|
|
Thanks o_e_l_e_o. I appreciate your feedback. What if however I wanted to send a transaction from my own node and the mempool is already clogged up beyond the 300 MB cap for most nodes with other transactions (maybe with inscriptions, ordinals etc.)? Maybe my transaction never gets to a miner's mempool since it's already full how then would it get confirmed? I think nowadays the default amount of nodes that your node connects to is only 10, right? What if this is some sly roundabout way to allow transactions to be made on CEXs/authorized transmitters or something like that? Anyway I really hope I'm just being paranoid and ignorant of the technical operations here but this seems quite odd to me.
If your fee is higher then the fees that in the TXs being dropped then you will just push a lower fee TX out of their mempool. It's not something you should worry about. There are also a lot of well connected nodes and services that will broadcast your TX https://live.blockcypher.com/btc/pushtx/You don't even need to be running core, you can build your TX manually using python (and other code too) and push it out through a variety of ways. -Dave
|
|
|
Since this is a bit out of character for you would you be willing to sign a message with one of your old BTC addresses that you have posted? Just seems off that someone who lives on TG as much as you usually do is locked out. Take your pick: Paranoid people live longer. Just because you are paranoid does not mean that they are not out to get you. Etc. With that being said and you proving you are you, I can do it but with 2 strings attached: 1) BTC no alts, I just don't have them. 2) Not in private. You post a BTC address I send to it and it's all out in the open. Dave looks down, Oh a signature for a privacy mixer. If you want to move it someplace else I hear this sinbad place works well. this way it's all public I sent the funds to you. -Dave Response to DaveF. Hope it proves the real me :-D I need it in USDT not in BTC. I am all in Bitcoin too LOL Since those alts are hard to hide and easy to treace the wallet address, I prefer PM so that it stays between me and the lender. This address is on my profile by the way for long time. 155Z69y6sFmMbJRvV4bdSRvn6ZXDLJ3v7i H0ddxFS9sBeuJ+LhIvpsYhOf01zHUiBpL8ryYpHuMutcLrFSnkRyCcY1NmAwWTn2h64v67uxa2Ja6iAUaebxXfA= Signature valid and address from years ago. I have the attitude that since at least certain admins can read PMs that they are not that much more private. But, I would be willing to do it in PM As for the USDT, I can't. Since I only have BTC and am US (NY) based if I trade it to USDT it's going to have to be on a regulated exchange and the tax man is going to show up asking for their cut. OR going to one of the non KYC exchanges through a VPN and paying the fees. If nobody else steps up and you want to take the BTC let me know. -Dave
|
|
|
|