|
I definitely lean towards being sexed in, but considering this requires at least one more member, I will accept being beat in.
Initiation by a cop is good, but not for me. I prefer the rest of the options more than the cop one.
Oh and just in case you decide to apply force, please make sure to be as gentle as you can, especially in the "beat in" option.
PS: I am on page 2 already!!!!
|
|
|
|
Then put it back and start making confusion in the forum. You may later con-fuse things too, but confusion is also a must =)))
The queen must announce the new scared puppy. She must do it here! Otherwise I am too scared to face the gatekeepers! By the way, I started reading the whole topic. See you in 2 years  |
|
|
|
I have taken permission from foxpup to use it If our queen allowed you we bow down to all her decision  But nobody knew about that and we gotta protect the gang  In the past that was supposed to be made by red tags =))) apogio, if you are here now, please understand that humor is a must among us Also understand the humor from my earlier post. I love humour mate. But I am new to this forum, so forgive me. I am the smallest puppy you could ever find in here. Yeap the queen allowed it! I have no reason to lie and then face her rage! Edit: I will wear my fur again only if she says it here, to avoid confusion with the PMs |
|
|
|
our gang. this group. It's a Club  Then I wish you all the best for your club. And sorry for the confusion we caused. But, once more, you are a very helpful club for all the members. So thanks for that. I am leaving, and I hope foxpup will prove that what I say is legit, cause I would want to clear my name. |
|
|
|
The next logical step after enforcing KYC for all financial institutions (including CEXes) is to prohibit KYCed wallets from transacting with non-KYCed wallets. This is already happening. There have been a whole bunch of centralized exchanges saying they will only allow deposits or withdrawals to other TRUST entities. TRUST stands for the Travel Rule Universal Solution Technology, and is essentially a list of fully centralized fully KYCed services which report everything to the US or other respective government. So not only can you not transact with non-KYCed services, but you can't even withdraw you coins to your own wallet. Soon you will have government approved KYCed bitcoin which is bought, held, and sold only on centralized exchanges and used only to chase fiat gains, and then you will have all bitcoin which is held in your own wallets and not in the custody of a centralized exchange, which you can use for anything you like but which the government will treat as criminal and malicious. This split has already begun, and very few of us seem to care. It is indeed happening. The question is, how will we be able to use our bitcoin if most of the people suddenly decide to use bitcoin in a government-approved manner. I mean we wanted bitcoin to be free for everyone, without any intermediaries. We wanted to get rid of all of this centralised manipulation. Now, I am worried more than ever. If I want to buy something from an online store, will my bitcoin be rejected, just because I didn't buy it from a CEX? |
|
|
|
***WARNING***WARNING***WARNING******IMPOSTER ALERT!!!***Apparently, after quitting from MixTum campaign, apogio enrolled (by himself?) in our gang. Hi. I am apogio. I have taken permission from foxpup to use it without getting paid because I wanted to support her group. This group has always been helpful with me and really cared about bitcoin. Please foxpup if you can, explain them. I don't wanna look like an imposter. I will remove it, because it causes misunderstandings. Cheers Edit: I will never share the PMs I exchanged with Foxpup without her permission, but I can guarantee you that my intention was to support the group and SHE allowed me to do it. Of course I didn't get paid. The only proper support I have ever got on this forum is from members of this group. This is why I wore it for 12 hours. But apparently, I can't wear it without getting paid and being properly enrolled, even though I had Foxpup's permission. Anyway. Good day to all of you. |
|
|
|
|
@icopress you have been a great lad. I will abstain from every kind of advertising / payments from this forum.
Thanks for working with me. Please remove me from the payroll, I have also sent you a PM.
Good luck to all who remain.
|
|
|
|
So today, I am in favor of using the WoS. It's smooth and works well. But yeah... custodial solution... For small amounts, I don't mind. Compared to the amount of money people keep in exchanges, it's tiny. I haven't tried it, but you can probably fund it from an exchange directly. Imagine topping up your Bitcoin LN wallet with a 5 sat transaction fee What is more curious, however, is that even when I have an open channel with WoS's node, sometimes payments fail from my node, but succeed from WoS app. Anyway, I will figure this out when I have the time. Sending funds from an exchange directly to WoS sounds good, but I don't use exchanges since I met you guys here I was tought not to... WoS has a built-in button that you can use to buy BTC from MoonPay. I have no idea how it works though. And I won't try it, I guess. |
|
|
|
For instance: Wallet of Satoshi.
I was against WoS because of it being custodial. After 6 months, I can say I use it more than my own LN node. It works flawlessly for me, due to the fact thar WoS nodes are connected with a ton of nodes. So sometimes, if I wanna pay someone, I will try to use my own node but there have been times where I couldn't pay due to the fact that there was no payment route between me and the other end. With WoS I never had this issue. So today, I am in favor of using the WoS. It's smooth and works well. But yeah... custodial solution... |
|
|
|
Links to other tutorials from the series:[BitcoinTalk Node Tutorial #2] Installing Electrs from source https://bitcointalk.org/index.php?topic=5477339.0[BitcoinTalk Node Tutorial #3] Sparrow terminal / infinite Whirlpool mixes https://bitcointalk.org/index.php?topic=5470024.0[BitcoinTalk Node Tutorial #4] Connecting BISQ to our node https://bitcointalk.org/index.php?topic=5478756.0[BitcoinTalk Node Tutorial #5] Hosting a Monero node on the same machine https://bitcointalk.org/index.php?topic=5480371.0Size required on disk:$ sudo du -sh /media/apogio/BTC/bitcoincore
627G /media/apogio/BTC/bitcoincore
I will create a series of posts (at my own slow pace).
In this series, I will create a custom Bitcoin Node on a GUI-less OS.
I will add various features on this node.
I encourage all of you to share your thoughts and suggestions. In fact, some decisions will be determined by your suggestions.
Hardware / Software used in the series| Computer | Raspberry Pi 4b 8GB RAM | | Software | Raspberry Pi OS Lite (64-bit) | | Storage | 2TB external SSD |
Installing and running Bitcoin Core on Raspbian LiteDownloading Bitcoin CoreFirstly, we create a directory on the home path, where we will download the necessary packages, let's say we create it inside the Downloads directory: mkdir -p ~/Downloads/Core
cd ~/Downloads/Core
Now, the latest version is 25.1, so the following command will download the core software and the checksum in our directory: wget https://bitcoincore.org/bin/bitcoin-core-25.1/bitcoin-25.1-aarch64-linux-gnu.tar.gz
wget https://bitcoincore.org/bin/bitcoin-core-25.1/SHA256SUMS
Let's check whether the checksum is correct: sha256sum --ignore-missing --check SHA256SUMS
So, now we must extract the installer from the tarball: tar -xvf bitcoin-25.1-aarch64-linux-gnu.tar.gz
Personally, I install my binaries in /usr/local/bin, so I will use the following command: sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-25.1/bin/*
We must be done, let's check: We should receive a prompt that the version is 25.1. Let's delete the directory we created to download the stuff we needed. It's no longer necessary: cd ~;
rm -rf ~/Downloads/Core
Most of the time, when the external storage is connected, it mounts to a specific filesystem location. Let's check where it is: This will return something like: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
...
sdb 8:16 0 1.9T 0 disk
`-sdb1 8:17 0 1.9T 0 part /media/apogio/BTC
...
From this, we can see that the external drive is mounted on /media/apogio/BTC. This will be our home directory for Bitcoin Core. Let's create a configuration file and start Bitcoin Core: cd /media/apogio/BTC
mkdir bitcoincore
nano bitcoin.conf
This will open up nano and create a file called bitcoin.conf inside the directory /media/apogio/BTC/bitcoincore. The following lines are ok for the moment: datadir=/media/apogio/BTC/bitcoincore
dbcache=5000
daemon=1
server=1
Now we are ready to go. Let's run Bitcoin Core and wait until the IBD is finished: bitcoind -conf=/media/apogio/BTC/bitcoincore/bitcoin.conf
This will take some days. So relax and let it work. If at any time you wish to stop the daemon, just run: bitcoin-cli --datadir=/media/apogio/BTC/bitcoincore stop
The IBD is finished, I will stop Bitcoin Core, and I will refresh my bitcoin.conf file as follows: # basic directives
datadir=/media/apogio/BTC/bitcoincore
# bitcoin daemon
daemon=1
server=1
listen=1
# tor
proxy=127.0.0.1:9050
bind=127.0.0.1
# network
rpcuser=<my user>
rpcpassword=<my pass>
[main]
rpcbind=127.0.0.1
rpcbind=<the local ip of my RPi>
rpcallowip=127.0.0.1
rpcallowip=192.168.0.0/16
# optimimizations
maxconnections=30
|
|
|
|
I been thinking about Bitcoin wallets and their safety (hot wallets) when people getting hacked, how often is it because someone get access to their seed phrase? But if you don't back up your wallet. Can they still hack your wallet then? You got no seed phrase, so they cant take that way. right? Or....? Please help a n00b here to understand.
If you don't backup your wallet, you are essentially helpless. The simplest scenario is that you (for any reason) lose access to the app that you have installed on your phone, or laptop and you have absolutely no way to restore the wallet. Having a hot wallet (as Charles-Tim said) can lead to wallet being compromised due to malware etc, but not backing it up, you are helpless against the strongest enemy, which is the human error. |
|
|
|
wow.. you are a cool person because you can see bitcoin as bitcoin while I can't, I see bitcoin in fiat rate.
Naah, not a very cool person, but thanks. Are you planning not to exchange bitcoins and will use bitcoins as a currency, not as an asset, so that you can view bitcoins in sats, not fiat exchange rates?
Exactly. However, life is life, so in case something bad happens to me and I need to convert BTC to FIAT, I will definetely do it, unless Bitcoin is so widely adopted that I can use it as it is. The plan is to use it as money, not as a means to get more FIAT money. |
|
|
|
Anyone else feeling same way?
Personally, not at all mate, I always look at my BTC as a total amount of sats and I never look at the exchange rate. So let's say I hold 0.1 BTC, I never make the translation in dollars. I like accumulating BTC so much I know I am not the average person, because I don't view Bitcoin as an investment but as better money, so I try to hold as much as I can of this type of money. By the way, I am not buying much BTC at the moment, because I have some real-life issues and I don't have a lot to save, but if I did, I would buy no matter what the exchange rate was. (Not a financial advice). |
|
|
|
|
I am very happy that Bitcoin becomes more widespread in the Balkans.
Kudos to all of you in Bulgaria.
If I visit Sofia, I will definetely visit the bar and I will pay with LN.
|
|
|
|
My password is probably around 10 digits
since 10 digits can be cracked very quickly.
10 digits implies that it consists only of numbers in the range 0 to 9? What we do know is: * "Officials said they did not use the conventional BIP standard algorithm". * The seed phrase alone doesn't produce the same set of addresses as it did in the past. So it must be something similar to the BIP-39 passphrase, meaning it appends to the seed phrase and produces another set of keys. OP, have you tried importing the words to Electrum? Just in case they use the same standard that Electrum does. Also, do you recall if they also offered LN features? Because they could potentially use aezeed cipher seed EDIT: I just saw you posted a valid BIP39 seed phrase. I hope it's not yours. |
|
|
|
Nope. A hdparm speed test doesn't care about the filesystem.
So the current speeds have gone up to: /dev/sda:
Timing cached reads: 1666 MB in 2.00 seconds = 834.15 MB/sec
Timing buffered disk reads: 328 MB in 3.15 seconds = 104.15 MB/sec
I feel stupid, but here is what happened... I was using the USB 2.0 port and not the 3.0 port. |
|
|
|
I can't find an English review for this exact model, but my Intenso USB stick is faster than what you get.
Perhaps a format will solve the issue... |
|
|
|
Which SSD do you have exactly?
This is my disk: https://www.amazon.de/-/en/Intenso-Internal-Inch-SATA-Black/dp/B0B63HPPG3I'm just guessing here: is it possible you're using a very low quality USB cable? Have you tried Gnome Disks? It has a Benchmark feature. Or have a look at GSmartControl, see if it can give you a reason for the low speed. No errors unfortunately... with GSmartControl Could the format be an issue? My disk is exfat EDIT: I think I will backup my drive and then format to ext4 |
|
|
|
Most microSD cards are faster than this nowadays. It should be 10 times faster:
Did you run your disk speed test during IBD? If so, that's probably why it's slow.
The type of SSD matters too: some perform just as you'd expect, and others are only fast "in short burst", and after writing the burst data, it gets much slower, up to the point that combined read and writes can make the entire system freeze for a while. That doesn't matter much for normal computer usage, but it matters a lot during heavy tasks (such as the IBD).
Hi Loyce. No my IBD is finished and my node is stopped. So essentially my RPi is connected to an SSD which has the whole bitcoin-core structure, but bitcoind is not running. I also ran fstrim -v on the mounted directory and it trimmed some data, but it didn't work afterwards. I mean no amelioration was seen. |
|
|
|
I wanted to test it further, so I did: To my surprise, I got: /dev/sda:
Timing cached reads: 1776 MB in 2.00 seconds = 888.80 MB/sec
Timing buffered disk reads: 62 MB in 4.67 seconds = 13.28 MB/sec
Isn't it too slow for an SSD ? Especially the second timer. |
|
|
|
|
Show Posts
