Since September, the month that I found out about the existence of signature campaigns, I've been accepted on 7 in total. What I never understood is the form of appliance.

The majority of the campaign managers ask you to:

• Wear the avatar and the signature. (Sometimes it's written to do it before applying)
• And reply by filling out a form like this:

Code:

Bitcointalk Profile Link:
Current post count (Including this one):
BTC Address:
Merit EARNED in the last 120 days:

1) Why would I need to post my profile link? Isn't it obvious that I'm the user that applies for the campaign? Are there applicants who entered a different link than the one of their profile?

2) Why do they ask you to wear the avatar and the signature, but they accept applicants whether they wear it or not? Obviously, once they're accepted they'll wear it, but it doesn't seem that this requirement has any point at all.

Disclaimer: I will delete low-quality posts. We all know what's a low quality post, I don't have to define it.
The fungibility of Bitcoin is a serious topic that requires discussion. I hope we all agree that having our transactions publicly announced won't make ours coins fungible. Truth be told, our beloved Bitcoin can't work same like as cash, because cash doesn't leave footprints. A dollar is equal with a dollar no matter who transacted it with who. Οn the contrary, a block chain analysis may be enough to prove that my inputs have a connection with a criminal activity and be censored for that. Recently, I read that despite the mixing and the coinjoining, there are centralized services that will decline “tainted” bitcoins.

It then comes to my mind that once there will be really less bitcoins left to be mined, like two decades later, the miners will have a better income from the transaction fees instead. Right now, every 10 minutes, 6.25 freshly mined and “whitelisted” bitcoins are brought into circulation. But, after we've mined most of them, we'll use the already mined bitcoins for our transactions.

If that's true, then the system will be filled with “tainted” bitcoins in the long term, as there'll always be criminal activity. Your thoughts.

[pure code]

I want to perform EC multiplication, but with pure code. No libraries or anything outside my C# class. I've found a ruby script (from learnmeabitcoin) that performs this procedure in pure ruby, but I am not sure that I understand these terms. I do have understood theoretically how ECC works, but in its maths, it seems impossible to make any sense. In other words, I may be able to “convert” the ruby code to C# line-by-line, but I won't have acknowledged the importance of each line. (which is what takes the cake, but anyway)

That being said, it'd really satisfy me if there's an already written code (just like in learnmeabitcoin) in C#. I've searched for it, but I only found complicated scripts that require libraries. I only want the “private key to public key” part. Not anything extra.


If there isn't one, please be my guide and tell me what I'm doing wrong.

Alright, so to implement EC multiplication, I'll have to also write the modular inverse, EC addition and EC doubling.

I turned this:

Code:

# Modular Inverse - Ruby doesn't have a built-in function for finding modular inverses, so here's one using the extended Euclidean algorithm.
def modinv(a, m = $p)
  a = a % m if a < 0 # make sure a is positive
  prevy, y = 0, 1
  while a > 1
    q = m / a
    y, prevy = prevy - q * y, y
    a, m = m % a, a
  end
  return y
end

Into this:

Code:

 public BigInteger modinv(BigInteger a, BigInteger m)
        {
            BigInteger prevy = 0;
            BigInteger y = 1;
            BigInteger q;
            if(a > 0)
            {
                a = a % m;
            }
            while(a > 1)
            {
                q = m / a;
                y = prevy - q * y;
                prevy = y;
                a = m % a;
                m = a;
            }
            return y;
        }

This:

Code:

# Double - Add a point on the curve to itself.
def double(point)
  # slope = (3x^2 + a) / 2y
  slope = ((3 * point[:x] ** 2) * modinv((2 * point[:y]))) % $p # using modular inverse to perform "division"

  # new x = slope^2 - 2x
  x = (slope ** 2 - (2 * point[:x])) % $p

  # new y = slope * (x - new x) * y
  y = (slope * (point[:x] - x) - point[:y]) % $p

  # return x, y coordinates of point
  return { x: x, y: y }
end

Into this:

Code:

public BigInteger[] ECdouble(BigInteger[] point){
            BigInteger slope = (3 * point[0] ^ 2) * modinv((2 * point[1]), p);
            BigInteger x = (slope ^ 2 - (2 * point[0])) % p;
            BigInteger y = (slope * (point[0] - x) - point[1]) % p;
            BigInteger[] coord = { x, y };
            return coord;
            
        }

This:

Code:

# Add - Add two points together.
def add(point1, point2)
  # double if both points are the same
  return double(point1) if point1 == point2

  # slope = (y1 - y2) / (x1 - x2)
  slope = ((point1[:y] - point2[:y]) * modinv(point1[:x] - point2[:x])) % $p

  # new x = slope^2 - x1 - x2
  x = (slope ** 2 - point1[:x] - point2[:x]) % $p

  # new y = slope * (x1 - new x) - y1
  y = ((slope * (point1[:x] - x)) - point1[:y]) % $p

  # return x, y coordinates of point
  return { x: x, y: y }
end

Into this:

Code:

public BigInteger[] ECaddition(BigInteger[] point1, BigInteger[] point2)
        {
            if(point1 == point2)
            {
                return ECdouble(point1);
            }

            BigInteger slope = ((point1[1] - point2[1]) * modinv(point1[0] - point2[0], p)) % p;
            BigInteger x = (slope ^ 2 - point1[0] - point2[0]) % p;
            BigInteger y = ((slope * (point1[0] - x)) - point1[1]) % p;
            BigInteger[] coord = { x, y };
            return coord;
        }

And finally, this:

Code:

# Multiply - Use the double and add operations to quickly multiply a point by an integer (e.g. a private key).
def multiply(k, point = $g) # multiply the generator point by default
  # create a copy the initial starting point (for use in addition later on)
  current = point

  # convert integer to binary representation (for use in the double and add algorithm)
  binary = k.to_s(2)

  # double and add algorithm for fast multiplication
  binary.split("").drop(1).each do |char| # ignore first binary character
    # 0 = double
    current = double(current)

    # 1 = double and add
    if char == "1"
      current = add(current, point)
    end
  end

  # return the final point
  return current
end

Into this:

Code:

 public BigInteger[] ECMultiplication(BigInteger k, BigInteger[] Gpoint)
        {
            BigInteger[] current = g;
            string binary = String.Join(String.Empty,
              privatekey.Select(
                c => Convert.ToString(Convert.ToInt32(c.ToString(), 16), 2).PadLeft(4, '0')
              )
            );

            // ignoring the first binary character
            binary = binary.Substring(1);
            current = ECdouble(current);
            if (binary[0] == '1') {
                current = ECaddition(current, Gpoint);
            }
            return current;
        }

I run this:

Code:

BigInteger k = BigInteger.Parse(privatekey, NumberStyles.AllowHexSpecifier);
BigInteger[] point = ECMultiplication(k, g);
string x = point[0].ToString("X");
string y = point[1].ToString("X");
string public_key_uncompressed = "04" + x + y;
MessageBox.Show(public_key_uncompressed);

with this private key:

Code:

EF235AACF90D9F4AADD8C92E4B2562E1D9EB97F0DF9BA3B508258739CB013DB2

and I get as a result this uncompressed public key:

Code:

04F16342D6F4B64CC9911166A922D5AE5A9074B6BB59F3B7F159E82DFBB1F2641080931651B4F05BB9DD93ED3DF9D708BC0A1AD03F478767C3FDE73AEE2739C9ED54

I know that something goes wrong in that process since I get a different result from gobittest.appspot.com:

Is there a lot of account farming these days or is it just me? It gets annoying, because once I read the replies of a post I immediately realize that the original poster is a liar. The posts aren't off-topic, but there should be a rule to prevent this annoyance. The guy behind these accounts draws attention; it makes it pretty clear to understand that the accounts are related.

Take this for example: I bought my first 500 us dollars Bitcoin! [archive.org]. The first page is consisted of 18 alt accounts with the same activity/post count and no merits. You'll observe that the guy behind these accounts was just submitting meaningless posts and then logging out from each account to log in to the next one. Each post time difference is around 2 minutes. Then, he did it again 4 hours later.

Is there an actual bitcointalk account marketplace? How can this be really profitable for someone? I wouldn't pay more than two cents satoshis for such account.

I'm generally using my email to get notified for new replies on my posts or for new threads on sections I'm watching. Once I get the notification, I'll have to open the topicseen#new link, otherwise I'll stop getting notified about that thread.

The problem is that while I can visit the forum and check the “Show new replies to your posts.” whenever I want to see the replies to my posts, I don't have an alternative for the watching sections.

For example: If a new thread is created on a section I am following, I'll have to either open the link or simply stop getting notified about that section until I revisit it. I may read the email after a couple of hours and miss other threads that were created within that period. Thus, I ain't getting notified for (most of the) threads that I'm interested in. I was wondering if I'm the only one with that issue.

I was wondering if there's a script inside the source code that reveals to the electrum nodes that you're the owner of these addresses. If you are and decide to broadcast a transaction through an electrum node, you surely ruin your privacy, at least to that specific node. But if you don't broadcast anything, can they (or it if you're running with --one-server) see that you're the owner of these addresses or you query the balances same like on a watch-only wallet?

Additional questions:

• How do you know if a node uses SSL? I guess that if it does, it's better for your privacy since your ISP can't see that you're transferring a signed transaction.
• Wouldn't it be better if you broadcasted to a Bitcoin node directly? Just like when you run Bitcoin Core. The Bitcoin node can't know for sure if that's your transaction or if you're sharing transaction(s) from your mempool peer-to-peerly.

I want to buy a very cheap VPS running Ubuntu 18.04/20.04, the cheapest out there. The problem is that there is no guide showing the prices, I just googled "Ubuntu VPS" and got some results from digital ocean, but I may find cheaper packages here.

Requirements:

• 1 CPU.
• 500GB storage. (I want to run a full node)
• Bandwidth: Anything larger than 1TB.
• I think that 1GB RAM is fine.

I also want to pay in BTC.

[“syndrome”]

I have been in this forum for 1 year and I've noticed that the main motivation for making high quality posts is the fact that you can get paid out of it. While I'm a strong believer that signature campaigns enrich this forum's quality and that “it keeps it alive”, it is advisable to mention a downside of this procedure and specifically:  The “syndrome” of signature campaigns.

I'll speak out my personal view about this, it may not be true for everyone. Once I read the replies of a thread, I'll ignore most of the users that participate on a low-paying signature campaign, by the thought that they are shit posters. But, that may not be true. I observe a form of prejudice. I'll actually take a closer look to a post made by a high-quality signature campaign participant rather than a newbie.

A user may have thousands of merits, but he/she may create low quality posts. Someone with 4-digits post count and 2-digits merit count would be quickly rejected into your mind, either because he/she may have promoted failed/scam tokens or made shitty posts for pennies. But it's much more different with avatars/signatures. Most of the times, when I scroll a thread I'll skip those replies, without even looking at the merit/post count ratio. It just makes a splash! And that's because along with the avatars/signatures, I will have formed a bad picture of the ones that advertise it.

I wonder if this happens to you too, and if it does, do you hide avatars and signatures to prevent it? This poll may be a great feedback for the campaigns' owners too.

[Operating System]

Operating System: Ubuntu 18.04
Bitcoin Client: Bitcoin Core v0.21.0 release build.
Description of the problem: I run bitcoind with the parameters below and it works, but I then receive that "ThreadRPCServer incorrect password attempt from 127.0.0.1" error. It doesn't seem to change anything like stop working, but it just continuously returns it. What does it mean and how do I fix it?
Log file: https://pastebin.com/raw/Jbfq31Pw

Code:

angelo@angelocomputer:~/bitcoin/bin$ ./bitcoind -testnet -datadir=/media/angelo/1TB/p2p/BTC/AppData/testnet
2021-05-02T13:56:10Z Bitcoin Core version v0.21.0 (release build)
2021-05-02T13:56:10Z Assuming ancestors of block 000000000000006433d1efec504c53ca332b64963c425395515b01977bd7b3b0 have valid signatures.
2021-05-02T13:56:10Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000001db6ec4ac88cf2272c6
2021-05-02T13:56:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2021-05-02T13:56:10Z Default data directory /home/angelo/.bitcoin
2021-05-02T13:56:10Z Using data directory /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3
2021-05-02T13:56:10Z Config file: /media/angelo/1TB/p2p/BTC/AppData/testnet/bitcoin.conf (not found, skipping)
2021-05-02T13:56:10Z Setting file arg: wallet = ["test"]
2021-05-02T13:56:10Z Command-line arg: datadir="/media/angelo/1TB/p2p/BTC/AppData/testnet"
2021-05-02T13:56:10Z Command-line arg: testnet=""
2021-05-02T13:56:10Z Using at most 125 automatic connections (1024 file descriptors available)
2021-05-02T13:56:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-05-02T13:56:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-05-02T13:56:10Z Script verification uses 1 additional threads
2021-05-02T13:56:10Z scheduler thread start
2021-05-02T13:56:10Z HTTP: creating work queue of depth 16
2021-05-02T13:56:10Z Using random cookie authentication.
2021-05-02T13:56:10Z Generated RPC authentication cookie /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/.cookie
2021-05-02T13:56:10Z HTTP: starting 4 worker threads
2021-05-02T13:56:10Z Using wallet directory /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets
2021-05-02T13:56:10Z init message: Verifying wallet(s)...
2021-05-02T13:56:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2021-05-02T13:56:10Z Using wallet /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/wallet.dat
2021-05-02T13:56:10Z BerkeleyEnvironment::Open: LogDir=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/database ErrorFile=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/db.log
2021-05-02T13:56:10Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:12Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:12Z init message: Loading banlist...
2021-05-02T13:56:12Z SetNetworkActive: true
2021-05-02T13:56:12Z Using /16 prefix for IP bucketing
2021-05-02T13:56:12Z Cache configuration:
2021-05-02T13:56:12Z * Using 2.0 MiB for block index database
2021-05-02T13:56:12Z * Using 8.0 MiB for chain state database
2021-05-02T13:56:12Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-05-02T13:56:12Z init message: Loading block index...
2021-05-02T13:56:12Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2021-05-02T13:56:12Z Opening LevelDB in /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/blocks/index
2021-05-02T13:56:12Z Opened LevelDB successfully
2021-05-02T13:56:12Z Using obfuscation key for /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/blocks/index: 0000000000000000
2021-05-02T13:56:16Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:16Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:20Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:20Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:24Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:24Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:26Z LoadBlockIndexDB: last block file = 197
2021-05-02T13:56:26Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1536, size=24551924, heights=1972270...1973835, time=2021-04-21...2021-05-02)
2021-05-02T13:56:26Z Checking all blk files are present...
2021-05-02T13:56:27Z Opening LevelDB in /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/chainstate
2021-05-02T13:56:27Z Opened LevelDB successfully
2021-05-02T13:56:27Z Using obfuscation key for /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/chainstate: 7c064d8c1f4992c5
2021-05-02T13:56:27Z Loaded best chain: hashBestChain=000000000000000597c6d123f53e04725afc19c3efce9cefcde56d21cba01db7 height=1973817 date=2021-05-02T12:30:14Z progress=0.999989
2021-05-02T13:56:27Z init message: Rewinding blocks...
2021-05-02T13:56:28Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2021-05-02T13:56:28Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2021-05-02T13:56:28Z init message: Verifying blocks...
2021-05-02T13:56:28Z Verifying last 6 blocks at level 3
2021-05-02T13:56:28Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2021-05-02T13:56:28Z No coin database inconsistencies in last 6 blocks (65 transactions)
2021-05-02T13:56:28Z  block index           16661ms
2021-05-02T13:56:28Z init message: Loading wallet...
2021-05-02T13:56:28Z BerkeleyEnvironment::Open: LogDir=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/database ErrorFile=/media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/wallets/test/db.log
2021-05-02T13:56:29Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:29Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:29Z [test] Wallet File Version = 169900
2021-05-02T13:56:29Z [test] Keys: 2004 plaintext, 0 encrypted, 20004 w/ metadata, 2004 total. Unknown wallet records: 0
2021-05-02T13:56:30Z [test] Wallet completed loading in            1825ms
2021-05-02T13:56:30Z [test] setKeyPool.size() = 2000
2021-05-02T13:56:30Z [test] mapWallet.size() = 3
2021-05-02T13:56:30Z [test] m_address_book.size() = 6003
2021-05-02T13:56:30Z block tree size = 1973836
2021-05-02T13:56:30Z nBestHeight = 1973817
2021-05-02T13:56:30Z Bound to [::]:18333
2021-05-02T13:56:30Z torcontrol thread start
2021-05-02T13:56:30Z Bound to 0.0.0.0:18333
2021-05-02T13:56:30Z Bound to 127.0.0.1:18334
2021-05-02T13:56:30Z loadblk thread start
2021-05-02T13:56:30Z init message: Loading P2P addresses...
2021-05-02T13:56:30Z UpdateTip: new best=000000000000000ffface17e209b2223a6af32dbf8cd89899316ad5467bb546e height=1973818 version=0x27ffe000 log2_work=74.209103 tx=59974529 date='2021-05-02T12:39:31Z' progress=0.999991 cache=0.0MiB(66txo)
2021-05-02T13:56:30Z UpdateTip: new best=000000000000000d56571094d7cf071c0c37c73208109fdad037d36390a05cfb height=1973819 version=0x27ffe000 log2_work=74.209138 tx=59974530 date='2021-05-02T12:40:54Z' progress=0.999991 cache=0.0MiB(67txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000002e5a4b5e28efa317ea2770697b4bce73a37b0141c72f37629 height=1973820 version=0x27ffe000 log2_work=74.209173 tx=59974537 date='2021-05-02T12:44:56Z' progress=0.999991 cache=0.0MiB(73txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000000b9d317a7f4c61437b1594f021b442496f523ed234eb64d0d height=1973821 version=0x37ffe000 log2_work=74.209208 tx=59974541 date='2021-05-02T12:46:14Z' progress=0.999991 cache=0.0MiB(83txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000053ef79138eddddaffc49329da54c4917586dc69957f5472cc height=1973822 version=0x20e00000 log2_work=74.209243 tx=59974546 date='2021-05-02T12:49:45Z' progress=0.999992 cache=0.0MiB(97txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000009b571e04159ce352ead96620f2001cb4c6c8e2db9709e39d9 height=1973823 version=0x37ffe000 log2_work=74.209278 tx=59974554 date='2021-05-02T12:52:55Z' progress=0.999992 cache=0.0MiB(107txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000226f9f493ad571350160511521c73b5fe4b01ef21a19f4a796 height=1973824 version=0x20800000 log2_work=74.209312 tx=59974557 date='2021-05-02T12:53:25Z' progress=0.999992 cache=0.0MiB(110txo)
2021-05-02T13:56:30Z UpdateTip: new best=000000000000001d927d04b24ec36301b3a4efcc2b453ebafce90f5babe1925f height=1973825 version=0x20c00000 log2_work=74.209347 tx=59974560 date='2021-05-02T12:55:49Z' progress=0.999993 cache=0.0MiB(116txo)
2021-05-02T13:56:30Z Loaded 18641 addresses from peers.dat  105ms
2021-05-02T13:56:30Z ERROR: DeserializeFileDB: Failed to open file /media/angelo/1TB/p2p/BTC/AppData/testnet/testnet3/anchors.dat
2021-05-02T13:56:30Z 0 block-relay-only anchors will be tried for connections.
2021-05-02T13:56:30Z init message: Starting network threads...
2021-05-02T13:56:30Z net thread start
2021-05-02T13:56:30Z init message: Done loading
2021-05-02T13:56:30Z addcon thread start
2021-05-02T13:56:30Z dnsseed thread start
2021-05-02T13:56:30Z Waiting 300 seconds before querying DNS seeds.
2021-05-02T13:56:30Z opencon thread start
2021-05-02T13:56:30Z msghand thread start
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000015f1a8125022f28c020d4573ce58c77c5cd73f8509efdd1fa1 height=1973826 version=0x20800000 log2_work=74.209382 tx=59974695 date='2021-05-02T13:04:12Z' progress=0.999994 cache=0.1MiB(606txo)
2021-05-02T13:56:30Z UpdateTip: new best=000000000000001c4cb918c0b06f00f33b69a7d600885d451de7142b5abf7fd3 height=1973827 version=0x20000000 log2_work=74.209417 tx=59974699 date='2021-05-02T13:05:19Z' progress=0.999994 cache=0.1MiB(612txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000072a1136c1f984f34835ee9eebbbcee630a720afca06b407a3 height=1973828 version=0x20000000 log2_work=74.209452 tx=59974704 date='2021-05-02T13:05:56Z' progress=0.999994 cache=0.1MiB(622txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000014f28c269d6f0ff73bbba4d4ae27363899e0820b67e31e7ad0 height=1973829 version=0x27ffe000 log2_work=74.209487 tx=59974731 date='2021-05-02T13:19:34Z' progress=0.999995 cache=0.1MiB(661txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000154c0d7a4834d24b8346b6c462eb5cfc25f9d9a2194f5cf9ed height=1973830 version=0x2fffe000 log2_work=74.209521 tx=59974740 date='2021-05-02T13:20:58Z' progress=0.999996 cache=0.1MiB(669txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000003069fef9f960461e64de898fca9dad8b5c854d791fae0abfb height=1973831 version=0x20400000 log2_work=74.209556 tx=59974741 date='2021-05-02T13:21:04Z' progress=0.999996 cache=0.1MiB(670txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000003bbdd8a679e303660070775ce8d90187dc01f3bce8baa0ea9 height=1973832 version=0x2fffe000 log2_work=74.209591 tx=59974748 date='2021-05-02T13:23:59Z' progress=0.999996 cache=0.1MiB(678txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000167fba394608a8fdb12f1b03fc999e8b6422fc37864e846887 height=1973833 version=0x20c00000 log2_work=74.209626 tx=59974754 date='2021-05-02T13:25:23Z' progress=0.999996 cache=0.1MiB(688txo)
2021-05-02T13:56:30Z UpdateTip: new best=0000000000000001bb991be3ce9f24e1bbcb9debcbf6dcc29cc69b6bffc4c3dd height=1973834 version=0x20c00000 log2_work=74.209661 tx=59974756 date='2021-05-02T13:26:10Z' progress=0.999996 cache=0.1MiB(690txo)
2021-05-02T13:56:30Z UpdateTip: new best=00000000000000169c3b43824cd93cb787bb3ab88f89af4526efb8b878413866 height=1973835 version=0x20200000 log2_work=74.209695 tx=59974768 date='2021-05-02T13:31:44Z' progress=0.999997 cache=0.1MiB(704txo)
2021-05-02T13:56:30Z Imported mempool transactions from disk: 0 succeeded, 13 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2021-05-02T13:56:30Z loadblk thread exit
2021-05-02T13:56:31Z Leaving InitialBlockDownload (latching to false)
2021-05-02T13:56:31Z New outbound peer connected: version: 70015, blocks=1973839, peer=0 (full-relay)
2021-05-02T13:56:33Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:33Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:37Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:37Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000009d4be98b8d8ece34b91bc323e8395eb7b8fc88c469e1f1584 height=1973836 version=0x27ffe000 log2_work=74.209730 tx=59974790 date='2021-05-02T13:43:24Z' progress=0.999998 cache=0.1MiB(736txo)
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000013bcf985eaebc79e5599c28ab4adb3b931cb92499a3cfa5272 height=1973837 version=0x20000000 log2_work=74.209765 tx=59974796 date='2021-05-02T13:46:59Z' progress=0.999999 cache=0.1MiB(739txo)
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000011338bdf80cd11484c2522ed38978d6806750585d216bcc46d height=1973838 version=0x20c00000 log2_work=74.209800 tx=59974799 date='2021-05-02T13:49:11Z' progress=0.999999 cache=0.1MiB(744txo)
2021-05-02T13:56:38Z UpdateTip: new best=0000000000000009080fa46b471b908099d8cc849f02774ac372e114c4cd9571 height=1973839 version=0x2fffe000 log2_work=74.209835 tx=59974825 date='2021-05-02T13:55:50Z' progress=1.000000 cache=0.1MiB(770txo)
2021-05-02T13:56:41Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438
2021-05-02T13:56:41Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:43Z New outbound peer connected: version: 70016, blocks=1973839, peer=1 (full-relay)
2021-05-02T13:56:44Z New outbound peer connected: version: 70015, blocks=1973839, peer=2 (full-relay)
2021-05-02T13:56:45Z New outbound peer connected: version: 70015, blocks=1973839, peer=3 (full-relay)
2021-05-02T13:56:45Z New outbound peer connected: version: 70016, blocks=1973839, peer=4 (full-relay)
2021-05-02T13:56:46Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39436
2021-05-02T13:56:46Z ThreadRPCServer incorrect password attempt from 127.0.0.1:39438

bitcoin.conf:

Code:

server=1
listen=1
daemon=1
txindex=1
rpcallowip=127.0.0.1

For some reason, once I enter the following command on the terminal I get this error:

Code:

angelo@angelopc:~/Desktop/bitcoin/bin$ ./bitcoin-cli --testnet --rpcuser=test123456 --rpcpassword=123456 --netinfo
error: Authorization failed: Incorrect rpcuser or rpcpassword

The thing is that these are the correct credentials, I haven't made any mistakes. Here's my bitcoin.conf:

Code:

server=1
listen=1
daemon=1
txindex=1
rpcuser=test123456
rpcpassword=123456

What is going on? FYI, the configuration file is located on an external drive, while the binaries of Bitcoin Core are on my internal SSD.

I'm reading the way multisig works (p2sh), but I haven't totally understood how you end up with this:

Code:

tb1q7zdkfcze59yz4ca9clslznd297xq68yvypkhz33ph34g62g0yxrqxd00gc

Correct me if I'm somewhere wrong:

The scriptPubKey is the hash of my script hash surrounded with HASH160 and EQUAL opcodes. According with an example of learnmeabitcoin, a scriptPubKey looks like that:

_OP_HASH160_ _script hash_ _OP_EQUAL_

or in hexadecimal:

Code:

a914748284390f9e263a4b766a75d0633c50426eb87587

Question #1: Why is the address above longer than a usual native segwit? Since we no longer pay to multisig (using P2MS) and we're locking the funds to a scriptPubKey that has a script hash of the N public keys, shouldn't the address length be the same whether the script hash was hashed requiring 1-of-1 or 15-of-15?

Question #2: How is the script hash come of? I haven't read that anywhere. On a simple address (that requires 1-of-1) it could be a hash of the compressed public key. Once you wanted to spend from that address you could reveal that public key along with a signature, the nodes could hash it to verify that it's the correct public key and validate the signature. What do you hash in this case?

HASH160(M, public keys ^{(ascending order)}, N) ?

Isn't N unnecessary that way?

I'll pay 10,000 satoshis for a pizza. Like maybe a large one, otherwise I'll consume it quickly. You can make the pizza yourself and bring it to my house or order it for me from a delivery place, but what I'm aiming for is getting food delivered in exchange for satoshis where I don't have to order or prepare it myself.

I like mushrooms, tomatoes and sausage. Please don't attempt to add any weird toppings like onions or fish.

Thanks,
BlackHatCoiner

(Sarcasm)

I have been experimenting with electrum as a wallet since I learnt about bitcoin, a year ago, and I can admit that it's the simplest and most useful one. I'd like to run my own electrum server, but not for privacy reasons, just for exercise. I also have bought a Windows VPS that isn't being used at the moment, so why not providing it to the electrum community?

I picked electrumx, because it's the most popular implementation. It seems that I can't install it on windows, only on unix. The thing is that I don't have an Ubuntu installed right now. Could this work with Windows 10 on an Ubuntu LTS?

Other questions too:

• Is the same procedure if I want to run a testnet server? I don't have the storage for downloading the entire blockchain.
• How does it return the balance of address(es) instantly? On Bitcoin Core it has to rescan the blockchain (which will take a lot of time).
• Will I be shown on others' network servers? If no, how can I be shown?

Whether you use an altcoin (or bitcoin) for a long or short-term investment, or because it satisfies you as a medium of exchange, it'd be misleading to call it a "currency". I don't know who began this terrible start of the use "currency" after "crypto", but, in my opinion, it shouldn't be formulated like that since none of them are currencies.

A currency is a system of money in general use in a particular country. For example fiat. Fiat money gives central banks greater control over the economy because they can control how much money is printed. This is how the state works.

Naming them "coins" isn't false, they can be considered as "coins" (Hence "altcoins"). In ancient times, people used to exchange goods with gold coins and there were times when they passed over their national currency with those coins. And that's because they were broadly accepted by anyone, since they were made out of gold.

I just wanted to state that I find it falsely to use the term "currency" over something that can be used by anyone in the world and it is definitely not determined or even acceptable by a nation.

I think that this should be a correct sub-board for this thread.

Hi, I've just noticed that if you recover a wallet by importing its seed phrase on electrum, it won't be stored anywhere on your hard drive. Alongside, if you normally create a wallet, the seed phrase can be found on the electrum wallet file (that has no extension).

Does this make any sense that I'm too dumb to understand? If you recover a wallet by that way, the master private key is stored on your hard drive, but not the seed phrase. Is there any reason why it stores only one child private key? Shouldn't there be a warning about that?

I want to replace Satoshi's genesis block with mine. I've generated a valid hash with Genesis Block Generator, but I'm getting this error once I run the compiled bitcoin-qt.exe:

Here's my block's information:

Code:

Hash: 000000003a7385e7dae9000662e5867c9330386f627d7b4e54386d9fe8d3d488
Nonce: 3407408574
Unix time: 1617893414
Public key (Uncompressed): 043b41c76ed8826d0341f82ac92c607c943fb8bfb5074ee4fbb0aab578369854e13e9ce3ff2318dfbb69bf30b9c5e4153b4bf6ab3c3396344d1501e42c19113afe
Block message: "3 September 1974, the foundation."
Merkle root hash: 148e8dd6467cd80a4aa037cc8931a4ee0e05b38bdb5b723ace9cd7212d525424

These are the modifications that I've made on chainparams.cpp: [Link]. What exactly do I do wrong?


Edit: Fortunately, I found the solution by myself. I didn't know that you'd have to replace the genesis.hashMerkleRoot with the byteswapped result. I believed that I should have put the merkle hash from the genesis block generator in there. What a happy ending.

On my way to fork Bitcoin Core, I had to either set the nMaxTipAge = DEFAULT_MAX_TIP_AGE * 10000 in validation.cpp (to avoid any gap troubles) or change the genesis block. I tried the first option, but now I want to change the genesis block and I have this query.

Why do I have to mine the genesis block? A forum member had posted an announcement thread of his project ([ANN] Genesis Block Generator), but it is described that you'll have to mine the genesis block.

Isn't mining necessary only when we want to proof a work? There's no proof of work on the genesis block, only the initial conditions to start the chain.

I've removed the vSeeds, changed the pchMessageStart and I'd like to make a connection from my home's node to my VPS'. I ran addnode "<MY_VPS_STATIC_IP>:2333" add and established a connection between these two computers. The problem is that the VPS node doesn't seem to send information to the home node. There's only one outcoming connection from the VPS.

This is what my home node shows:

I guess that's why I haven't received any block while I've mined two on the VPS. Do I have to port forward? Or I can solve this by changing a firewall rule?

I've changed the pngs/icos on share\pixmaps and their xmps. I then built Bitcoin Core and it had Bitcoin's icon, so I guess the executable's (bitcoin-qt.exe) and generally the program's logo isn't inside that directory. Do you know where I can find it?

Hi, I'm a newbie at mining, I have never mined any coins or helped a pool with my computational power, I just know the basics of how mining works. Some months ago I forked bitcoin core and wrote a guide of how to do it too, because I find it really interesting when you implement an idea ^{(that can be implemented)}. Although, the action is far from the theory. I found a lot of difficulties on my way.

I've solved some blocks on my forked Bitcoin Core, but I want to switch to cpuminer, since it's better to compute on the command line than on a UI. This is what I execute:

Code:

minerd --user rpcuser --pass 111111 --url http://127.0.0.1:8333/ --threads 4 --coinbase-addr 3B9dSAqGNSyPasdSrwbJZ2rLSgPmyt8bQQ --coinbase-sig "my test coins" -a sha256d -D

And this is what I get:

It has returned other errors on my forked Bitcoin Core, but I've ran it, above, on pruned Bitcoin Core (that follows the original bitcoin chain) and right now I get this. What am I doing wrong?