Pages:
Author

Topic: [ANN] Datacoin - Censorship-Free Data Storage - page 4. (Read 66848 times)

legendary
Activity: 2254
Merit: 1290
And I still can't send my dtc
I do not know what to do and how to take coins from the wallet
Turns out that the wallet is hard-coded by default to use segwit addresses and on a non-upgraded network, coins sent to segwit addresses are lost.

Don't use the 0.16.3 client, revert to either the 0.8.6 client or the Crossverse 0.15.99 client.

I've withdrawn the 0.16.3 release and deleted the repository as it's clear that supporting this particular upgrade is beyond my skillset.

If you have coins stuck on segwit addresses, PM me with the relevant 0.16.3 client privkey and I'll replace your coins.

Sad but true.

Cheers

Graham
member
Activity: 114
Merit: 10
still cant send my dtc anywere, tx id just wont get confirmed, reverting back to 8.6version
ive created a new listening node of v16.3 hope it solves my problem
addnode=198.199.70.169

And I still can't send my dtc
I do not know what to do and how to take coins from the wallet
hero member
Activity: 701
Merit: 511
still cant send my dtc anywere, tx id just wont get confirmed, reverting back to 8.6version
ive created a new listening node of v16.3 hope it solves my problem
addnode=198.199.70.169
hero member
Activity: 701
Merit: 511
still cant send my dtc anywere, tx id just wont get confirmed, reverting back to 8.6version
legendary
Activity: 2254
Merit: 1290
Latest list of recently-seen nodes, edited from bytestamp's peers list

addnode=102.165.224.64
addnode=103.246.152.226
addnode=103.246.152.233
addnode=112.198.79.59
addnode=112.95.235.238
addnode=113.10.158.207
addnode=113.10.242.157
addnode=114.79.37.60
addnode=117.34.72.3
addnode=122.192.218.102
addnode=144.76.118.44
addnode=144.76.64.49
addnode=146.199.233.66
addnode=150.143.250.57
addnode=175.139.175.82
addnode=192.186.4.213
addnode=202.114.29.51
addnode=204.48.92.37
addnode=204.48.92.48
addnode=213.31.19.33
addnode=213.31.19.87
addnode=213.31.19.98
addnode=218.57.139.132
addnode=221.194.44.178
addnode=221.194.44.198
addnode=221.194.44.205
addnode=27.145.61.18
addnode=45.63.115.238
addnode=50.17.6.175
addnode=51.148.146.204
addnode=54.193.18.89
addnode=54.193.64.123
addnode=54.206.54.159
addnode=58.218.199.216
addnode=58.218.199.248
addnode=89.73.143.76
addnode=91.250.62.26
addnode=95.217.78.168
addnode=graymines.net



Edit:
Meh, I fed them into my client, which can only connect to:

addnode=144.76.64.49
addnode=51.148.146.204
addnode=91.250.62.26

So yeah, there were only two listening nodes, now three - and two of them are my nodes, one remote, one local (configured with `upnp=1` so my router's UPNP allows external access to the standard 4777 port - but a static IP address is needed, won't work with network running behind a dynamic IP address).


Cheers

Graham
member
Activity: 114
Merit: 10

18:12:56

[
  {
    "id": 1,
    "addr": "91.250.62.26:4777",
    "addrlocal": "185.96.30.239:59758",
    "addrbind": "192.168.0.102:59758",
    "services": "0000000000000001",
    "relaytxes": true,
    "lastsend": 1623769976,
    "lastrecv": 1623769976,
    "bytessent": 351821,
    "bytesrecv": 57113861,
    "conntime": 1623769875,
    "timeoffset": 32,
    "pingtime": 0.354441,
    "minping": 0.354441,
    "version": 70001,
    "subver": "/Satoshi:0.8.3/",
    "inbound": false,
    "addnode": false,
    "startingheight": 1568979,
    "banscore": 0,
    "synced_headers": 1568979,
    "synced_blocks": -1,
    "inflight": [
    ],
    "whitelisted": false,
    "bytessent_per_msg": {
      "addr": 55,
      "getaddr": 24,
      "getheaders": 350889,
      "inv": 671,
      "ping": 32,
      "verack": 24,
      "version": 126
    },
    "bytesrecv_per_msg": {
      "addr": 32152,
      "headers": 57081396,
      "inv": 133,
      "pong": 32,
      "verack": 24,
      "version": 124
    }
  },
  {
    "id": 0,
    "addr": "144.76.118.44",
    "addrlocal": "185.96.30.239:59757",
    "addrbind": "192.168.0.102:59757",
    "services": "000000000000040d",
    "relaytxes": true,
    "lastsend": 1623769946,
    "lastrecv": 1623769963,
    "bytessent": 2022,
    "bytesrecv": 8450,
    "conntime": 1623769874,
    "timeoffset": 33,
    "pingtime": 0.042114,
    "minping": 0.042114,
    "version": 70015,
    "subver": "/Datoshi:0.16.3/",
    "inbound": false,
    "addnode": true,
    "startingheight": 4015228,
    "banscore": 0,
    "synced_headers": 4015234,
    "synced_blocks": 4015234,
    "inflight": [
    ],
    "whitelisted": false,
    "bytessent_per_msg": {
      "addr": 55,
      "feefilter": 32,
      "getaddr": 24,
      "getblocktxn": 58,
      "getdata": 374,
      "getheaders": 1117,
      "headers": 25,
      "ping": 32,
      "pong": 32,
      "sendcmpct": 99,
      "sendheaders": 24,
      "verack": 24,
      "version": 126
    },
    "bytesrecv_per_msg": {
      "addr": 1760,
      "block": 1797,
      "blocktxn": 989,
      "cmpctblock": 1410,
      "feefilter": 32,
      "getheaders": 1117,
      "headers": 1041,
      "ping": 32,
      "pong": 32,
      "sendcmpct": 66,
      "sendheaders": 24,
      "verack": 24,
      "version": 126
    }
  }
]
legendary
Activity: 2254
Merit: 1290
Current set of listening nodes:

Code:
addnode=213.31.19.87
addnode=89.73.143.76
addnode=144.76.118.44

Meh, wrong. Just tried to synch from 213.31.19.87 and 89.73.143.76,  can't connect to either from here.

Currently, the only listening nodes are:
Code:
addnode=144.76.118.44
addnode=91.250.62.26
It's worth ensuring you have both as addnodes, if not connects.

Cheers

Graham
legendary
Activity: 2254
Merit: 1290
And how to refuse to transfer later?
Transactions tab, select tx, right click, choose "Abandon transaction". Afterwards, optionally: Debug Window -> Wallet Repair -> Recover transactions.

Cheers

Graham
member
Activity: 114
Merit: 10
Coins are still not sent
It happens, it doesn't imply any error, just that the network is under-populated. Give it 24 hours, then if the tx hasn't gone through, abandon the tx and try again.

I cannot replicate your problem, I sent 10 DTC to freiexchange, confirming with no problems.

Cheers

Graham

And how to refuse to transfer later?
legendary
Activity: 2254
Merit: 1290
Coins are still not sent
It happens, it doesn't imply any error, just that the network is under-populated. Give it 24 hours, then if the tx hasn't gone through, abandon the tx and try again.

I cannot replicate your problem, I sent 10 DTC to freiexchange, confirming with no problems.

Cheers

Graham
member
Activity: 114
Merit: 10
Coins are still not sent
Cтaтyc: 0/unconfirmed, not in memory pool
Дaтa: 15.06.2021 08:47
To: freiexchange DDFuWNPHqf9H475n7BTfS4oy8hhgCHWfSF
Debit: -998.67500000 DTC
Transaction fee: -1.32500000 DTC
Net amount: -1000.00000000 DTC
Transaction ID: 93cf832df09094c97fea66ec5b7c26ab4fd66e88904b173a6ca4862960354296
Transaction total size: 1325 bytes
Output index: 0
legendary
Activity: 2254
Merit: 1290
getpeerinfo

    "addr": "144.76.118.44",
    "inbound": false,

    "addr": "91.250.62.26:4777",
    "inbound": false,

Looks okay. Those are the (atm, only) two nodes that are configured to listen (listen=1) and process/confirm txes.

Cheers

Graham
member
Activity: 114
Merit: 10

16:04:19

getpeerinfo


16:04:19

[
  {
    "id": 2,
    "addr": "144.76.118.44",
    "addrlocal": "185.96.30.239:53034",
    "addrbind": "192.168.0.102:53034",
    "services": "000000000000040d",
    "relaytxes": true,
    "lastsend": 1623762254,
    "lastrecv": 1623762254,
    "bytessent": 2358,
    "bytesrecv": 12797,
    "conntime": 1623762014,
    "timeoffset": 33,
    "pingtime": 0.042556,
    "minping": 0.041925,
    "version": 70015,
    "subver": "/Datoshi:0.16.3/",
    "inbound": false,
    "addnode": true,
    "startingheight": 4014581,
    "banscore": 0,
    "synced_headers": 4014602,
    "synced_blocks": 4014602,
    "inflight": [
    ],
    "whitelisted": false,
    "bytessent_per_msg": {
      "addr": 55,
      "feefilter": 32,
      "getaddr": 24,
      "getdata": 640,
      "getheaders": 1117,
      "headers": 25,
      "ping": 96,
      "pong": 96,
      "sendcmpct": 99,
      "sendheaders": 24,
      "verack": 24,
      "version": 126
    },
    "bytesrecv_per_msg": {
      "addr": 1760,
      "block": 2918,
      "cmpctblock": 4699,
      "feefilter": 32,
      "getheaders": 1117,
      "headers": 1519,
      "inv": 61,
      "ping": 96,
      "pong": 96,
      "sendcmpct": 66,
      "sendheaders": 24,
      "tx": 259,
      "verack": 24,
      "version": 126
    }
  },
  {
    "id": 3,
    "addr": "91.250.62.26:4777",
    "addrlocal": "185.96.30.239:53037",
    "addrbind": "192.168.0.102:53037",
    "services": "0000000000000001",
    "relaytxes": true,
    "lastsend": 1623762249,
    "lastrecv": 1623762174,
    "bytessent": 764678,
    "bytesrecv": 120361807,
    "conntime": 1623762018,
    "timeoffset": 32,
    "pingtime": 0.171037,
    "minping": 0.171037,
    "version": 70001,
    "subver": "/Satoshi:0.8.3/",
    "inbound": false,
    "addnode": false,
    "startingheight": 1464487,
    "banscore": 0,
    "synced_headers": 1466368,
    "synced_blocks": -1,
    "inflight": [
    ],
    "whitelisted": false,
    "bytessent_per_msg": {
      "addr": 55,
      "getaddr": 24,
      "getheaders": 762982,
      "inv": 1403,
      "ping": 64,
      "verack": 24,
      "version": 126
    },
    "bytesrecv_per_msg": {
      "addr": 32152,
      "headers": 120322182,
      "inv": 7261,
      "pong": 64,
      "verack": 24,
      "version": 124
    }
  }
]
legendary
Activity: 2254
Merit: 1290
writes an error in the console

addnode 213.31.19.87 add

Error: Node already added (code -23)

As long as you see 144.76.118.44 in the list of peers (enter getpeerinfo in the console or check the "Peers" tab), your client should be able to sync.

Cheers

Graham
member
Activity: 114
Merit: 10
In the config I have these lines for entering

addnode 213.31.19.87 add
addnode 89.73.143.76 add
addnode 144.76.118.44 add
member
Activity: 114
Merit: 10
I can't figure out how to write correctly

Either:
open the console and enter:
Code:
addnode 213.31.19.87 add
addnode 89.73.143.76 add
addnode 144.76.118.44 add

Or add the lines:
Code:
addnode=213.31.19.87
addnode=89.73.143.76
to the datacoin.conf file - see example datacoin.conf here:

https://github.com/datacoinproject/datacoin/releases/download/0.16.3.1/example.datacoin.conf

writes an error in the console
15:13:42

addnode 213.31.19.87 add


15:13:42

Error: Node already added (code -23)

Cheers

Graham

legendary
Activity: 2254
Merit: 1290
I can't figure out how to write correctly

Either:
open the console and enter:
Code:
addnode 213.31.19.87 add
addnode 89.73.143.76 add
addnode 144.76.118.44 add

Or add the lines:
Code:
addnode=213.31.19.87
addnode=89.73.143.76
to the datacoin.conf file - see example datacoin.conf here:

https://github.com/datacoinproject/datacoin/releases/download/0.16.3.1/example.datacoin.conf

Cheers

Graham
member
Activity: 114
Merit: 10
Current set of listening nodes:

Code:
addnode=213.31.19.87
addnode=89.73.143.76
addnode=144.76.118.44

Cheers,

Graham


Good day. How to apply them
on your debug console just write addnode "ip" add

I can't figure out how to write correctly
hero member
Activity: 701
Merit: 511
Current set of listening nodes:

Code:
addnode=213.31.19.87
addnode=89.73.143.76
addnode=144.76.118.44

Cheers,

Graham


Good day. How to apply them
on your debug console just write addnode "ip" add
member
Activity: 114
Merit: 10
Current set of listening nodes:

Code:
addnode=213.31.19.87
addnode=89.73.143.76
addnode=144.76.118.44

Cheers,

Graham


Good day. How to apply them
Pages:
Jump to: