Why doesn't condoras have Legendary rank yet? I'd say we apply this: some people got screwed by this, and if they have decent posts, by all means, give them the 250 or 500 merit that they need to rank-up. I've just sent condoras the maximum (50 Merit). He needs 105 more. To make it easier: those are his previously Merited posts: I just sent some merits to condoras. If anyone bother show few good posts posted by him (since i don't bother check all 140 merit tx shown by LoyceV), i might send more. |
|
|
|
That's extremely inefficient. You will end up with a lot of files that are so tiny (176-300 bytes) and opening each file and reading it is still consuming the biggest percentage of the total time.
Don't forget the bloat due to filesystem block size (these days most filesystem have 4KB as default block size). I want to program the database itself, which makes it possible, more or less. It's worth a try.
Consider taking course on Database. Or just run Electrum server locally and disable the rate limit. |
|
|
|
1. Checkout the version I want git checkout 4405b78d6059e536c36974088a8ed4d9f0f29898 Actually it's not first version. There are few older version which can be found at https://satoshi.nakamotoinstitute.org/code/. - has someone successfully compiled the first version on Linux? seems to me that the versions is "targeting" only windows users. Is this correct?
Correct, very early version of Bitcoin Qt only target Windows. If you check old discussion, few user criticize Satoshi due to Windows only build. - did you also have the same issues? how did you solve it
I never tried running old version, but i would download compiled version and run it with WINE. |
|
|
|
Most of your question is about SegWit, not about soft-fork in general. I also heard people saying that SegWit is actually a block size increase. Wait what? So you can do a soft fork to increase the block size, and Bitcoin Core clients installed in 2015 and never updated will accept those blocks as valid and add those blocks to their Block Chain?
1. SegWit could increase block size through block size because the witness part is removed and the block size have size 1MB or less. 2. Old client will treat those block as valid block, but they don't perform verification on transaction which use SegWit. So what is to prevent me from doing my own soft fork? Let's call my soft fork SegCash, and then I buy a bunch of mining equipment and start mining my own blocks. Will those blocks that follow my own soft fork rules be accepted by all the other nodes?
There are many aspect which prevent you from doing it, but mainly it's because 1. Community support. 2. How do you make your change backward compatible. |
|
|
|
The firewall must be defused for the connection: sudo ufw allow from 192.168.0.0/16 to any port 3002 comment 'allow BTC RPC Explorer from local network'
sudo ufw status By default, the ufw firewall is disabled on Ubuntu. So it's optional to do this step, unless you want to secure your computer/server by configuring firewall. ufw by default is initially disabled
So if you want to thank, do not thank me, but @NeuroticFish who has done the main work!
More guide which specify source/environment won't hurt though  |
|
|
|
If you bother use Bitcoin OPCODES, why don't you just create software with good UI/UX or add such feature to existing open-source wallet (such as Electrum)? Wallet such as Electrum already support custom script (such as OP_RETURN), so we just need someone to make it more user-friendly. Service idea is simple
Deposit savings amount , handler takes 1% and deposits the rest to desired wallet with attached nlock.
If i'm going to use 3rd party to lock my Bitcoin, i would rather use service such as BlockFi which give me some interest rather than losing 1% of my coin. |
|
|
|
I do, I've successfully recovered both wallets (Electrum and Metamask) and they are up and running on another computer.
Just confirming, did you only enter the seed phrase or also move the coin to newly generated wallet? If you did the former and the technician have malicious intent, he/she/they still could steal the coin. Even if data loss is presented, both wallets are fine, however, my only concern would be the technician to snoop through my files, which may sound too paranoid (or not, you never know).
Without knowing technician history or license, your concern is normal. |
|
|
|
The actual checksum used in encoding is the result of "polymod" XORed with a constant. This constant is 0x01 for Bech32 (BIP-173) encoding just flipping the least significant bit and is 0x2bc830a3 for Bech32m (BIP-350) encoding. The former is used for witness version 0 addresses and the later for 1+. This is basically the only difference that was introduced in BIP-350. Thanks for the explanation, it's simpler than i think. Guess i missed it because BIP 173 never use word "constant" when they mention 0x01.
@Coding Enthusiast do you have any plan to create Bech32m version of this guide since the BIP already created and few wallet already implement it?
i dont understand why they needed to have bech32m if they already have bech32. the more address types that get created i think the worse that is for bitcoin not better. i dont know if anyone else feel that way or not especially though if the address type that is being changed had some type of issue with it that motivated the creation of a related address typing. but i guess they'll keep going. watch out for bech32P anytime soon.  Here's why. On a side note, most people won't be able to tell difference between Bech32 and Bech32m. At least unless they know Bech32m is used since witness version 1 which indicated by Bech32 address with prefix bc1p. MotivationBIP173 defined a generic checksummed base 32 encoded format called Bech32. It is in use for segregated witness outputs of version 0 (P2WPKH and P2WSH, see BIP141), and other applications. Bech32 has an unexpected weakness: whenever the final character is a 'p', inserting or deleting any number of 'q' characters immediately preceding it does not invalidate the checksum. This does not affect existing uses of witness version 0 BIP173 addresses due to their restriction to two specific lengths, but may affect future uses and/or other applications using the Bech32 encoding. This document addresses that by specifying Bech32m, a variant of Bech32 that mitigates this insertion weakness and related issues. |
|
|
|
"Didn't you use a passphrase when you were creating the wallet on Wasabi?" This was the problem. Now it worked. thanks man In case it's not obvious, seed generated by Wasabi is useless if you don't remember the passphrase. I would recommend you to write few hint of the passphrase alongside with the seed. because Electrum seed (as it was mentioned are not BIP39) are generated in a way that they will not be a valid BIP39 mnemonic and should be rejected by wallets validating such seed phrases!
why would they want to avoid being complaint with a standard. That doesn't make any sense. did they just do a "roll your own" kind of thing and think it's better for some reason? almost every other wallet is compliant they aren't. go figure. What they actuall do is creating new standard. Imagine BIP 39 and "Electrum Seed Version System" as HDMI and DisplayPort. |
|
|
|
|
Have you tried using legacy address format (which start with character "1")? AFAIK CGMiner development halted few years ago and doesn't support Bech32/native segwit address.
P.S. Solo mining isn't practical these days, i would recommend you to join pool instead.
|
|
|
|
According to CoinTelegraph, China’s National Development and Reform Commission (CNDRM) is now seeking public opinion on the inclusion of crypto mining in its list of “phased-out” industries
Only this part of this news which seems to be true (after using google transaction on the source), while the rest is opinion/speculation. I doubt there'll be any drastic action anytime soon. |
|
|
|
And inside nano editor: cd ./electrs/target/release
./electrs CTRL-X and Save This script will fail if you run it from different location (location when you run nano to create the script). You should replace it with absolute path. |
|
|
|
Do you have any good suggestions for me?
1. What OS do you use? 2. Do you need to unlock the USB on different OS? If you only use Linux, use LUKS since most distro support it. But if you use different OS and you wish to unlock the USB on multiple OS, i don't know what option is available for you. One more option I was thinking about is to install separate portable linux OS on my USB stick and use it only for purpose of keeping my backup stuff.
That's the better option, the OS will have encryption options too including login password and user folder encryption (not encrypting the whole disk). Although this is also intensive and reduces disk lifespan. Here is an ancient guide that still works: https://bitcointalk.org/index.php?topic=853288.0While it works, i would recommend Tails instead since it's easier to use. |
|
|
|
Since CMC is owned by Binance, this reflect how poor Binance manage security of their service (especially if it's not their main service). Apparently, only the email addresses were leaked, so your account and diamonds are safe but you should still be cautious, you might start getting some phishing attacks sent to your email.
Not if you're also victim of different data leak which leak the password and use same/very-similar password on different website. |
|
|
|
Learning how to open up my port 8333 on my router. Issue with this is that ipconfig is showing a different IP address then whatismyip.
IP shown by ipconfig is your local IP (which given by your router). |
|
|
|
I was hoping for some sort of docker setup.
I made short guide about setup Electrum using docker few months ago. Honestly if the VPS use linux, you can use easy installer/docker (which i mentioned above), which is very easy to use. I saw the docker, but I haven't ever used docker in the past for setups. Would you mind guiding me a hand? There's no steps, just a “ docker run /” script. I rarely use Docker, but here's short guide (i've tested it on my device, but don't know whether it runs on WSL) 1. Install docker sudo apt install docker.io
2. Test whether docker run correctly sudo docker run hello-world
If you see message "Hello from Docker!", then Docker run correctly. 3. Create directory which used to store electrumx data cd /home/user
mkdir electrumx
4. Run this command sudo docker run \
-v /home/user/electrumx:/data \
--net="host" \
-e DAEMON_URL=username:password@localhost \
-e COIN=Bitcoin \
-e NET=testnet \
-p 50002:50002 \
lukechilds/electrumx
Here's short explanation 1. --net="host", this command is used to ensure the container can access host port. 2. -e used to configure environment for electrumx. 3. -p HOST_PORT:CONTAINER_PORT is used to expose and link port between host and container. 4. -v HOST_DIRECTORY:CONTAINER_DIRECTORY is used to link host directory on the container. 5. lukechilds/electrumx means container we're going to use P.S. If you want ElectrumX container to automatically start after boot, add --restart=always when you run docker. |
|
|
|
I'm not sure an article that calls Taproot a "hard" fork is worth reading, and surely enough after skimming through the article it is filled with other small and big mistakes. A funny one: " signature algorithm allows users to generate public and private keys."! What do you expect from sponsored post/article? For the most part, the average Bitcoin
Core wallet users will need to upgrade their client to the new version, but for everyone else, there’s nothing to do.
Yet, anyone that want to make use of Taproot has to update his wallet if the new wallet version update support it. The sentence you quoted refer to Taproot activation, so Bitcoin Core user also not required to upgrade the software due to backward compatibility. |
|
|
|
but i am not able to find my nodes ip address and user name and password. Ive been searching for hours on how to get this info but nothing is popping up.
For RPC username/password, you're supposed to configure it manually from bitcoin.conf or as parameter when you launch Bitcoin Core. Here's an example for bitcoin.conf, where rpcallowip is used to protect your node from brute-force attempt. server=1
rpcuser=your_username
rpcpassword=your_password
rpcallowip=1.2.3.4
As for your node IP address, it should be IP given by your ISP. To verify whether it works, restart your Bitcoin Core and run this command. bitcoin-core.cli -rpcuser=your_username -rpcpassword=your_password getnetworkinfo
|
|
|
|
My background is primarily in the PHP programming language, but I'm a relative beginner in Python
FYI, there are some cryptocurrency project which use PHP programming language. You can read the code and learn how it works and gain some experience and also you can look at the issues to see if you can contribute.
Here's an additional tip, some repository have label "Good first issue" which should be suitable for new contributor who're not familiar with the project yet. |
|
|
|
|
Show Posts
