[DVC]DevCoin - Official Thread - Moderated

[Unthinkingbit]

Thanks FuzzyBear for the information.

I see only one tough problem with what they ask:

..
In case of losing clients' funds due to forks or technical / security issues with block chain or node, you as developer will bear financial responsibility.

This is open ended, and could wipe out anyone. It is unreasonable, and I don't think any developer has ever given out money if there was a problem in their code. Is that language in the application for other exchanges?

[1714305206]

1714305206

[1714305206]

1714305206

[1714305206]

1714305206

[1714305206]

1714305206

[accountantfuttock]

Does the team have experience in this sphere?

[FuzzyBear]

I think it is just a general clause to try cover themselves should the blockchain fork they want no responsibility for funds lost through a fork or network going wrong.  The actual wording for who can submit a coin is open ended:

"If you are a developer or official representative of cryptocurrency asset, you can add this asset to Livecoin."

So a non developer can submit the application and thus the last clause is invalid?

I feel it is more them saying if u submit a coin and it is not updated to  avoid security issues or forks and the exchange looses funds then you are responsible for not informing the exchange to update the code or providing the updated code with security patches applied as and when... they want to cover themselves listing any coins that are just going to be under developed and left potentially leaving security risks on their serveres running the exchanges etc...

Anyway I sent them in an application and got this as a reply:

04.12.2017 09:44
Hello.
Unfortunately, this year we no longer accept new assets.

...so maybe try in the new year? or should we look around for other possible listings?

Fuzzybear

Thanks FuzzyBear for the information.

I see only one tough problem with what they ask:

..
In case of losing clients' funds due to forks or technical / security issues with block chain or node, you as developer will bear financial responsibility.

This is open ended, and could wipe out anyone. It is unreasonable, and I don't think any developer has ever given out money if there was a problem in their code. Is that language in the application for other exchanges?

[IconFirm]

How about bisq? It's the only one I trust actually, apart from localbitcoins of course, but we can't list it there.

[develCuy]

How about bisq? It's the only one I trust actually, apart from localbitcoins of course, but we can't list it there.

More info about Bisq and how to list a new coin there: https://github.com/bisq-network/docs/blob/master/exchange/howto/list-token.adoc

[sawa]

I'm worried that my wallet got stuck on block 303999
Though in http://italyiimp.com/explorer it is shown that already the block 305335

If I delete and reload block chain, then on block 303999 I have this error:

Code:

In receiver.h, getIsSufficientAmount rejected the addresses or amounts.
For the given:
Height: 304000
Share: 4500000000000
Step: 4000
The expected addresses are:
The receiverMap shows that they should get 0 coins
The shares per address however are set to 4500000000000
15MZRa1cPUVChs6XpzyAfGox5nvPVpSvok

The given addresses are:
1KZKMYixw4PDtu5ZbKqrahRWeAgputuVoc

The given amounts are:
4500000000000

I have all receiver files:

Code:

.devcoin/receiver# ls
charity            receiver_12.csv  receiver_17.csv  receiver_21.csv  receiver_26.csv  receiver_30.csv  receiver_35.csv  receiver_3.csv   receiver_44.csv  receiver_49.csv  receiver_53.csv  receiver_58.csv  receiver_62.csv  receiver_67.csv  receiver_71.csv  receiver_76.csv                                            
random_number.txt  receiver_13.csv  receiver_18.csv  receiver_22.csv  receiver_27.csv  receiver_31.csv  receiver_36.csv  receiver_40.csv  receiver_45.csv  receiver_4.csv   receiver_54.csv  receiver_59.csv  receiver_63.csv  receiver_68.csv  receiver_72.csv  receiver_7.csv                                             
receiver_0.csv     receiver_14.csv  receiver_19.csv  receiver_23.csv  receiver_28.csv  receiver_32.csv  receiver_37.csv  receiver_41.csv  receiver_46.csv  receiver_50.csv  receiver_55.csv  receiver_5.csv   receiver_64.csv  receiver_69.csv  receiver_73.csv  receiver_8.csv                                             
receiver_10.csv    receiver_15.csv  receiver_1.csv   receiver_24.csv  receiver_29.csv  receiver_33.csv  receiver_38.csv  receiver_42.csv  receiver_47.csv  receiver_51.csv  receiver_56.csv  receiver_60.csv  receiver_65.csv  receiver_6.csv   receiver_74.csv  receiver_9.csv                                             
receiver_11.csv    receiver_16.csv  receiver_20.csv  receiver_25.csv  receiver_2.csv   receiver_34.csv  receiver_39.csv  receiver_43.csv  receiver_48.csv  receiver_52.csv  receiver_57.csv  receiver_61.csv  receiver_66.csv  receiver_70.csv  receiver_75.csv  update_receivers.sh

I added receiver_77.csv from git: //github.com/Unthinkingbit/charity.git, but the synchronization stops at block 303999.

Code:

devcoind getinfo
{
    "version" : 80501,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 303999,
    "timeoffset" : 0,
    "connections" : 4,
    "proxy" : "",
    "difficulty" : 391033605.64058393,
    "testnet" : false,
    "keypoololdest" : 1512497504,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

As if someone made their receiver_77.csv before that official receiver_77.csv posted to the git: //github.com/Unthinkingbit/charity.zhit and the chain goes on an incomprehensible fork

I before synchronization completely delete the block chain, leave only the devcoin.conf and files in the directory ~/.devcoin/ receiver
Here are all the peers of my wallet:

Code:

devcoind getpeerinfo
[
    {
        "addr" : "176.9.25.79:52333",
        "services" : "00000001",
        "lastsend" : 1512590947,
        "lastrecv" : 1512591406,
        "bytessent" : 496044,
        "bytesrecv" : 15553651,
        "conntime" : 1512497634,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305723,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "64.71.72.56:52333",
        "services" : "00000001",
        "lastsend" : 1512591250,
        "lastrecv" : 1512591405,
        "bytessent" : 305235,
        "bytesrecv" : 188895,
        "conntime" : 1512497635,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305723,
        "banscore" : 0
    },
    {
        "addr" : "104.168.155.119:52333",
        "services" : "00000001",
        "lastsend" : 1512591405,
        "lastrecv" : 1512591406,
        "bytessent" : 41469505,
        "bytesrecv" : 629147913,
        "conntime" : 1512497835,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305723,
        "banscore" : 0
    },
    {
        "addr" : "87.98.182.171:52333",
        "services" : "00000001",
        "lastsend" : 1512590246,
        "lastrecv" : 1512591406,
        "bytessent" : 53465402,
        "bytesrecv" : 855416984,
        "conntime" : 1512553938,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305804,
        "banscore" : 0
    }
]

Has anyone tried to synchronize blocks from scratch lately?
I think that there is a problem in the DVC network.

[FuzzyBear]

I synced up the other day no issues or problems. did it from scratch on new laptop also.

What version and client you running?  V 0.8.5.1?

Fuzzybear

I'm worried that my wallet got stuck on block 303999
Though in http://italyiimp.com/explorer it is shown that already the block 305335

If I delete and reload block chain, then on block 303999 I have this error:

Code:

In receiver.h, getIsSufficientAmount rejected the addresses or amounts.
For the given:
Height: 304000
Share: 4500000000000
Step: 4000
The expected addresses are:
The receiverMap shows that they should get 0 coins
The shares per address however are set to 4500000000000
15MZRa1cPUVChs6XpzyAfGox5nvPVpSvok

The given addresses are:
1KZKMYixw4PDtu5ZbKqrahRWeAgputuVoc

The given amounts are:
4500000000000

I have all receiver files:

Code:

.devcoin/receiver# ls
charity            receiver_12.csv  receiver_17.csv  receiver_21.csv  receiver_26.csv  receiver_30.csv  receiver_35.csv  receiver_3.csv   receiver_44.csv  receiver_49.csv  receiver_53.csv  receiver_58.csv  receiver_62.csv  receiver_67.csv  receiver_71.csv  receiver_76.csv                                            
random_number.txt  receiver_13.csv  receiver_18.csv  receiver_22.csv  receiver_27.csv  receiver_31.csv  receiver_36.csv  receiver_40.csv  receiver_45.csv  receiver_4.csv   receiver_54.csv  receiver_59.csv  receiver_63.csv  receiver_68.csv  receiver_72.csv  receiver_7.csv                                             
receiver_0.csv     receiver_14.csv  receiver_19.csv  receiver_23.csv  receiver_28.csv  receiver_32.csv  receiver_37.csv  receiver_41.csv  receiver_46.csv  receiver_50.csv  receiver_55.csv  receiver_5.csv   receiver_64.csv  receiver_69.csv  receiver_73.csv  receiver_8.csv                                             
receiver_10.csv    receiver_15.csv  receiver_1.csv   receiver_24.csv  receiver_29.csv  receiver_33.csv  receiver_38.csv  receiver_42.csv  receiver_47.csv  receiver_51.csv  receiver_56.csv  receiver_60.csv  receiver_65.csv  receiver_6.csv   receiver_74.csv  receiver_9.csv                                             
receiver_11.csv    receiver_16.csv  receiver_20.csv  receiver_25.csv  receiver_2.csv   receiver_34.csv  receiver_39.csv  receiver_43.csv  receiver_48.csv  receiver_52.csv  receiver_57.csv  receiver_61.csv  receiver_66.csv  receiver_70.csv  receiver_75.csv  update_receivers.sh

I added receiver_77.csv from git: //github.com/Unthinkingbit/charity.git, but the synchronization stops at block 303999.

Code:

devcoind getinfo
{
    "version" : 80501,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 303999,
    "timeoffset" : 0,
    "connections" : 4,
    "proxy" : "",
    "difficulty" : 391033605.64058393,
    "testnet" : false,
    "keypoololdest" : 1512497504,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

As if someone made their receiver_77.csv before that official receiver_77.csv posted to the git: //github.com/Unthinkingbit/charity.zhit and the chain goes on an incomprehensible fork

I before synchronization completely delete the block chain, leave only the devcoin.conf and files in the directory ~/.devcoin/ receiver
Here are all the peers of my wallet:

Code:

devcoind getpeerinfo
[
    {
        "addr" : "176.9.25.79:52333",
        "services" : "00000001",
        "lastsend" : 1512590947,
        "lastrecv" : 1512591406,
        "bytessent" : 496044,
        "bytesrecv" : 15553651,
        "conntime" : 1512497634,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305723,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "64.71.72.56:52333",
        "services" : "00000001",
        "lastsend" : 1512591250,
        "lastrecv" : 1512591405,
        "bytessent" : 305235,
        "bytesrecv" : 188895,
        "conntime" : 1512497635,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305723,
        "banscore" : 0
    },
    {
        "addr" : "104.168.155.119:52333",
        "services" : "00000001",
        "lastsend" : 1512591405,
        "lastrecv" : 1512591406,
        "bytessent" : 41469505,
        "bytesrecv" : 629147913,
        "conntime" : 1512497835,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305723,
        "banscore" : 0
    },
    {
        "addr" : "87.98.182.171:52333",
        "services" : "00000001",
        "lastsend" : 1512590246,
        "lastrecv" : 1512591406,
        "bytessent" : 53465402,
        "bytesrecv" : 855416984,
        "conntime" : 1512553938,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.5.1/",
        "inbound" : false,
        "startingheight" : 305804,
        "banscore" : 0
    }
]

Has anyone tried to synchronize blocks from scratch lately?
I think that there is a problem in the DVC network.

[FuzzyBear]

How about bisq? It's the only one I trust actually, apart from localbitcoins of course, but we can't list it there.

More info about Bisq and how to list a new coin there: https://github.com/bisq-network/docs/blob/master/exchange/howto/list-token.adoc

That looks interesting and a better approach to getting developed coins added by requiring unit tests to be written for address validation etc

Fuzzybear

[sawa]

I synced up the other day no issues or problems. did it from scratch on new laptop also.

What version and client you running?  V 0.8.5.1?

v 0.8.5.1

[develCuy]

Regarding official repo... I have a fork of the coinzen on my account here https://github.com/FuzzyBearBTC/devcoin-1 but I also have another fork from knotwork's cherry picked repo https://github.com/FuzzyBearBTC/devcoin I am concerned at the ownership of the coinzen repo as the forum coinzen has now long gone.  I dont mind hosting the official repo but would like to clear up the old one if not needed etc.

@FuzzyBear welcome back! I control the official repo, if you want access to it, just let me know, Devcoin needs lots of love!

[develCuy]

..
What needs to be done to "maintain that list"? If its hosting said files and editing them from time to time, i'm up for it. If that's not what has to be done, please tell us more about it.

You and K1773R both agreed to do it. Thank you both for offering. Looking over the last account file with the ongoing list in it:
https://github.com/Unthinkingbit/charity/blob/master/account_73.csv

I see that K1773R already has an administrator position, and you don't. In general, I want the administrative functions to be spread out, so that if an administrator leaves only one or two duties are dropped at a time, rather than a few at a time. So I prefer that you do it. However, it's up to you and K1773R, if you both decide that K1773R should do it that's fine with me. Please contact K1773R and decide between you who should take the position.

K1773R says that he agrees to let me take care of this duty.

confirmed

@Unthinkingbit, is my mirror being included in account_xx.csv? I don't see it in 76, nor in 77, maybe that has something to do with the sync issue? I got two seed nodes, they are not syncing anymore.

[develCuy]

ALSO: It has come to my attention that to compile devcoin, and other coins that old, against Boost 1.58 instead of 1,54 you need the following sed command's effect:

Code:

sed -i 's/<const\ CScriptID\&/<CScriptID/' rpcrawtransaction.cpp

Maybe someone can make the corresponding change in the git repo?

-MarkM-

Code is pushed to master branch long time ago: https://github.com/coinzen/devcoin/commit/ea4b51021ef98fd928320cbd1469460b93a0b33c

[wiser]

Any news on finding a new exchange for Devcoin since the abrupt departure of Coingather?

On another note, have admin lines been added to the more recent receiver files yet?

[Guido]

some updates about coingather which was dvc only exchange and where many millions of dvc were held and btc ltc etc

https://twitter.com/PoppCh/status/936889871280435200

if to be believed we know who it is

and apparently fbi investigating, why such a small exchange i don't know, but it 'may' come back
https://twitter.com/PoppCh/status/936929360333983744

even not people have smoked him out and know who he is

https://twitter.com/bling_bar/status/937168091242549248

so some possibilities but new exchange needed anyway

[Unthinkingbit]

We need an exchange for devcoin, and the more exchanges the better. I suggest a 60 share bounty for the first person(s) to get devcoin on another exchange, 40 shares for the next person on another exchange, and 20 shares for the next. Any objections?

Any news on finding a new exchange for Devcoin since the abrupt departure of Coingather?
..

some updates about coingather which was dvc only exchange and where many millions of dvc were held and btc ltc etc
..
so some possibilities but new exchange needed anyway

[Wekkel]

No objections from my side.

[wiser]

We need an exchange for devcoin, and the more exchanges the better. I suggest a 60 share bounty for the first person(s) to get devcoin on another exchange, 40 shares for the next person on another exchange, and 20 shares for the next. Any objections?

Any news on finding a new exchange for Devcoin since the abrupt departure of Coingather?
..

some updates about coingather which was dvc only exchange and where many millions of dvc were held and btc ltc etc
..
so some possibilities but new exchange needed anyway

Great idea. I'm all for it.

[develCuy]

We need an exchange for devcoin, and the more exchanges the better. I suggest a 60 share bounty for the first person(s) to get devcoin on another exchange, 40 shares for the next person on another exchange, and 20 shares for the next. Any objections?

Good move!

[spudsintegers]

how many tokens in total are you issuing?

[IconFirm]

how many tokens in total are you issuing?

What are you talking about?

Read the thread, or at least read the OP.....

Edit: Just read your post history. Spammer.