Bitcoin Forum
May 12, 2024, 10:32:46 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: My transactions get stuck in memory pool !!!  (Read 424 times)
chameleon123 (OP)
Jr. Member
*
Offline Offline

Activity: 48
Merit: 17


View Profile
January 10, 2019, 05:41:12 PM
 #21

Finally I got the answer!
As I previously said you can use legacy addresses but it is not a long term viable solution. You should fork 0.17+.

Thank you for all the help. I truly appreciate it.
No problem  Smiley

But It's still ambiguous to me why segwit address would fail creating block....
Because Segwit was not activated yet so you could not add Segwit transactions in a block.
"segwit address would fail creating block" : this is not the address which creates a block, it is the software. Block generation is (almost) unrelated to addresses.

I forked 0.17.1 and applied all my changes again(segwit activated by default), still didn't work with segwit addresses. This is strange!
1715553166
Hero Member
*
Offline Offline

Posts: 1715553166

View Profile Personal Message (Offline)

Ignore
1715553166
Reply with quote  #2

1715553166
Report to moderator
1715553166
Hero Member
*
Offline Offline

Posts: 1715553166

View Profile Personal Message (Offline)

Ignore
1715553166
Reply with quote  #2

1715553166
Report to moderator
1715553166
Hero Member
*
Offline Offline

Posts: 1715553166

View Profile Personal Message (Offline)

Ignore
1715553166
Reply with quote  #2

1715553166
Report to moderator
It is a common myth that Bitcoin is ruled by a majority of miners. This is not true. Bitcoin miners "vote" on the ordering of transactions, but that's all they do. They can't vote to change the network rules.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
darosior
Sr. Member
****
Offline Offline

Activity: 279
Merit: 435


View Profile
January 10, 2019, 06:42:03 PM
Merited by DarkStar_ (4)
 #22

Finally I got the answer!
As I previously said you can use legacy addresses but it is not a long term viable solution. You should fork 0.17+.

Thank you for all the help. I truly appreciate it.
No problem  Smiley

But It's still ambiguous to me why segwit address would fail creating block....
Because Segwit was not activated yet so you could not add Segwit transactions in a block.
"segwit address would fail creating block" : this is not the address which creates a block, it is the software. Block generation is (almost) unrelated to addresses.

I forked 0.17.1 and applied all my changes again(segwit activated by default), still didn't work with segwit addresses. This is strange!
Indeed.. Can you post a getrawtransaction decoded so we can check if this is the locktime again (if this is still the same function which returns false) ?
chameleon123 (OP)
Jr. Member
*
Offline Offline

Activity: 48
Merit: 17


View Profile
January 10, 2019, 06:57:11 PM
Merited by DarkStar_ (4), bones261 (1)
 #23

Quote
Indeed.. Can you post a getrawtransaction decoded so we can check if this is the locktime again (if this is still the same function which returns false) ?

Yes,
Code:
getrawtransaction 828bc6179345284921e70d393efe14cb42e0f9413752b126fb031a8f5a9c29ff 1
{
  "txid": "828bc6179345284921e70d393efe14cb42e0f9413752b126fb031a8f5a9c29ff",
  "hash": "9c6e3b45d40c4740180e16412e2d1861a1f94085f697ce42b7ffcbdd8086ec5a",
  "version": 2,
  "size": 247,
  "vsize": 166,
  "weight": 661,
  "locktime": 12,
  "vin": [
    {
      "txid": "2ca69f469e0b461c546e151441ba8537ef4a00615f9ae87ce5c97b72f7a76114",
      "vout": 0,
      "scriptSig": {
        "asm": "00147ff93bf12b29683c2c918f890f98cd19eb2c23b2",
        "hex": "1600147ff93bf12b29683c2c918f890f98cd19eb2c23b2"
      },
      "txinwitness": [
        "30440220629eb58313c3d6e95c7e22d5d130cb55e6ec7e288bfefdaf8ef4d7be5e908626022065805fbcd3dbb2cb859cb83f9164d3e39f929025c847546dd0552d595a641c6801",
        "038259d51458e3063ed5b9dc1fb8030fc6371cef44c674cf44e8ca2127f4110902"
      ],
      "sequence": 4294967293
    }
  ],
  "vout": [
    {
      "value": 45.99894100,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_HASH160 c0daf191bc75d4bd94b87590762005081b9ab71a OP_EQUAL",
        "hex": "a914c0daf191bc75d4bd94b87590762005081b9ab71a87",
        "reqSigs": 1,
        "type": "scripthash",
        "addresses": [
          "3KGjwqyqo6nnvzAcTCyAVTgdKJ3DwyPTXF"
        ]
      }
    },
    {
      "value": 2.00000000,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_HASH160 37fdd042f4dfad0e52fa932291a1cfafa7704892 OP_EQUAL",
        "hex": "a91437fdd042f4dfad0e52fa932291a1cfafa770489287",
        "reqSigs": 1,
        "type": "scripthash",
        "addresses": [
          "36o59NF7NbtWoLrAXBBtcGTSQ6wTiVRthV"
        ]
      }
    }
  ],
  "hex": "020000000001011461a7f7727bc9e57ce89a5f61004aef3785ba4114156e541c460b9e469fa62c00000000171600147ff93bf12b29683c2c918f890f98cd19eb2c23b2fdffffff0254d02c120100000017a914c0daf191bc75d4bd94b87590762005081b9ab71a8700c2eb0b0000000017a91437fdd042f4dfad0e52fa932291a1cfafa770489287024730440220629eb58313c3d6e95c7e22d5d130cb55e6ec7e288bfefdaf8ef4d7be5e908626022065805fbcd3dbb2cb859cb83f9164d3e39f929025c847546dd0552d595a641c680121038259d51458e3063ed5b9dc1fb8030fc6371cef44c674cf44e8ca2127f41109020c000000"
}
The problem is still with sequence number which is fffffffd.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!