Transactions not confirmed (0.3.80 Namecoin clients)

Post Reply
cassini
Posts: 332
Joined: Sun May 26, 2013 6:36 pm

Transactions not confirmed (0.3.80 Namecoin clients)

Post by cassini » Tue Mar 21, 2017 6:53 pm

Yesterday one of the mining pools (Slush) has finally updated their mining infrastructure. Slush was the last one of the larger mining pools that accepted all transactions from older Namecoin software. This means that half of the transactions from 0.3.80 clients or older will be unconfirmed forever! (Technical explanation in BIP-0062)

The best advice here is obviously: upgrade to Namecoin Core.

For the cases a user can't upgrade for whatever reason, I'll try to find a workaround and post it here a.s.a.p.
(it may become something like this: delete the pending transaction using deletetransaction. Then simply try again, and you get another chance the transaction gets confirmed. You may have to try again, though.)

PeerName
Posts: 8
Joined: Mon Apr 27, 2015 4:39 pm
os: linux
Contact:

Re: Transactions not confirmed (0.3.80 Namecoin clients)

Post by PeerName » Wed Mar 22, 2017 5:41 pm

I try to update but Namecoin 0.13.99-name-tab-beta1 client does not want to sync. It is not connecting. I only see "No block source available" message.

I tried on different machines with different versions of Linux. I even tried on my Raspberry Pi. Every time it's the same, zero connections to Namecoin network.

Anyone with this problem? Any ideas how to resolve it?

Edit: I tried another Internet provider. It starts to sync but stops on every ~2000 blocks. If I restart the client it downloads another 2000 blocks and stops. I must restart the client every minute if I want to sync it. It is not possible.

johnc
Posts: 89
Joined: Sun Dec 28, 2014 10:03 am

Re: Transactions not confirmed (0.3.80 Namecoin clients)

Post by johnc » Thu Mar 23, 2017 11:16 am

how many connections do you get?. if you reach 9 or more it's guaranteed that it will eventually sync; If not, consider opening the port 8334 if you don't have upnp enabled.

biolizard89
Posts: 1971
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Transactions not confirmed (0.3.80 Namecoin clients)

Post by biolizard89 » Fri Mar 24, 2017 12:06 am

cassini wrote:Yesterday one of the mining pools (Slush) has finally updated their mining infrastructure. Slush was the last one of the larger mining pools that accepted all transactions from older Namecoin software. This means that half of the transactions from 0.3.80 clients or older will be unconfirmed forever! (Technical explanation in BIP-0062)

The best advice here is obviously: upgrade to Namecoin Core.

For the cases a user can't upgrade for whatever reason, I'll try to find a workaround and post it here a.s.a.p.
(it may become something like this: delete the pending transaction using deletetransaction. Then simply try again, and you get another chance the transaction gets confirmed. You may have to try again, though.)
If a user has already issued a non-BIP62-compliant transaction with 0.3.80, and they then upgrade to Core, will the transaction automatically get canceled, or do they need to delete it manually? Someone has contacted us on Twitter to ask about this.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

biolizard89
Posts: 1971
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Transactions not confirmed (0.3.80 Namecoin clients)

Post by biolizard89 » Fri Mar 24, 2017 12:56 am

PeerName wrote:I try to update but Namecoin 0.13.99-name-tab-beta1 client does not want to sync. It is not connecting. I only see "No block source available" message.

I tried on different machines with different versions of Linux. I even tried on my Raspberry Pi. Every time it's the same, zero connections to Namecoin network.

Anyone with this problem? Any ideas how to resolve it?

Edit: I tried another Internet provider. It starts to sync but stops on every ~2000 blocks. If I restart the client it downloads another 2000 blocks and stops. I must restart the client every minute if I want to sync it. It is not possible.
First, do the following from a terminal:

Code: Select all

dig namecoindnsseed.digi-masters.com
dig namecoindnsseed.digi-masters.uk
dig nmc.seed.quisquis.de
dig dnsseed.namecoin.webbtc.com
The above seed addresses are from https://github.com/namecoin/namecoin-co ... s.cpp#L147 .

You'll get something like this:

Code: Select all

[user@temp-dig-1 ~]$ dig namecoindnsseed.digi-masters.com

; <<>> DiG 9.10.4-P6-RedHat-9.10.4-3.P6.fc24 <<>> namecoindnsseed.digi-masters.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45308
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;namecoindnsseed.digi-masters.com. IN	A

;; ANSWER SECTION:
namecoindnsseed.digi-masters.com. 10800	IN CNAME HDRedirect-LB3-890977680.us-east-1.elb.amazonaws.com.
HDRedirect-LB3-890977680.us-east-1.elb.amazonaws.com. 48 IN A 54.85.127.70
HDRedirect-LB3-890977680.us-east-1.elb.amazonaws.com. 48 IN A 52.204.129.22

;; Query time: 201 msec
;; SERVER: 10.137.11.1#53(10.137.11.1)
;; WHEN: Thu Mar 23 19:25:29 CDT 2017
;; MSG SIZE  rcvd: 156

[user@temp-dig-1 ~]$ dig namecoindnsseed.digi-masters.uk

; <<>> DiG 9.10.4-P6-RedHat-9.10.4-3.P6.fc24 <<>> namecoindnsseed.digi-masters.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14850
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;namecoindnsseed.digi-masters.uk. IN	A

;; ANSWER SECTION:
namecoindnsseed.digi-masters.uk. 0 IN	A	92.242.140.2

;; Query time: 59 msec
;; SERVER: 10.137.11.1#53(10.137.11.1)
;; WHEN: Thu Mar 23 19:25:54 CDT 2017
;; MSG SIZE  rcvd: 76

[user@temp-dig-1 ~]$ dig nmc.seed.quisquis.de

; <<>> DiG 9.10.4-P6-RedHat-9.10.4-3.P6.fc24 <<>> nmc.seed.quisquis.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27992
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;nmc.seed.quisquis.de.		IN	A

;; ANSWER SECTION:
nmc.seed.quisquis.de.	3600	IN	A	144.76.39.233
nmc.seed.quisquis.de.	3600	IN	A	198.15.127.242
nmc.seed.quisquis.de.	3600	IN	A	185.83.219.64
nmc.seed.quisquis.de.	3600	IN	A	176.9.113.75
nmc.seed.quisquis.de.	3600	IN	A	62.63.157.78
nmc.seed.quisquis.de.	3600	IN	A	195.154.188.50
nmc.seed.quisquis.de.	3600	IN	A	47.89.183.30
nmc.seed.quisquis.de.	3600	IN	A	108.62.19.130

;; Query time: 612 msec
;; SERVER: 10.137.11.1#53(10.137.11.1)
;; WHEN: Thu Mar 23 19:26:17 CDT 2017
;; MSG SIZE  rcvd: 177

[user@temp-dig-1 ~]$ dig dnsseed.namecoin.webbtc.com

; <<>> DiG 9.10.4-P6-RedHat-9.10.4-3.P6.fc24 <<>> dnsseed.namecoin.webbtc.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20398
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;dnsseed.namecoin.webbtc.com.	IN	A

;; Query time: 3520 msec
;; SERVER: 10.137.11.1#53(10.137.11.1)
;; WHEN: Thu Mar 23 19:26:37 CDT 2017
;; MSG SIZE  rcvd: 56
Then, start Namecoin Core, and go to Help -> Debug Window -> Console. Pick an IP address from the "ANSWER SECTION" output of the "dig" commands, and type the following into the Console:

Code: Select all

addnode 1.2.3.4 add
Where 1.2.3.4 is an IP address from the "dig" "ANSWER SECTION" output. Keep doing this until you have a decent number of connections (Namecoin Core will max out at 8 by default).

Let us know if this works.
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

PeerName
Posts: 8
Joined: Mon Apr 27, 2015 4:39 pm
os: linux
Contact:

Re: Transactions not confirmed (0.3.80 Namecoin clients)

Post by PeerName » Fri Mar 24, 2017 7:50 am

It's working now. Thank you very much! :)

We are also running a Namecoin full node to support the network. We used its IP address.

biolizard89
Posts: 1971
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Transactions not confirmed (0.3.80 Namecoin clients)

Post by biolizard89 » Fri Mar 24, 2017 8:20 am

PeerName wrote:It's working now. Thank you very much! :)

We are also running a Namecoin full node to support the network. We used its IP address.
Awesome, glad to hear it's working for you now. :)
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

Post Reply