Devcoin(DVC) Source Code Updated to Bitcoin 0.8.x

[meta.p02]

I downloaded the devcoin client in the OP.

Overall, it seems okay so far (indexing the ~118K blocks will take much more time). However, there are some minor cosmetic errors:

1. The taskbar logo, the window icon and the "About Devcoin" logo are I0Coin.
2. In "Sign/Verify Message", the "Devcoin addresses" are actually I0Coin addresses.
3. "Pay To" says "Enter a Bitcoin address".

Other than that, I don't see any major problems. I'll wait further until the reindex is complete to update this post.

[FrictionlessCoin]

a couple other questions....

who administers the DVC distribution?

how do you actually get yourself in the distribution?

[sidhujag]

a couple other questions....

who administers the DVC distribution?

how do you actually get yourself in the distribution?

If your a bitcoin dev or can do devcoin dev than maybe ur on list for now..

alot of ppl forget we r eArly adopters fyi...

[FrictionlessCoin]

a couple other questions....

who administers the DVC distribution?

how do you actually get yourself in the distribution?

If your a bitcoin dev or can do devcoin dev than maybe ur on list for now..

alot of ppl forget we r eArly adopters fyi...

Are you on the list?   How did you get on the list?

I did the same work you did, but for IXC.

IXC had not been updated for 2 1/2 years.  So I made the effort to port it to the 0.8.6 code base.

However, I had to beg for funds here and I continue to have to beg for funds.

For some crazy reason, all these early adopters believe that they can do nothing and the the coin they bought would magically rise in value.   Well,  there are other coins out there that have more aggressive development and marketing budgets.   Some even focus their efforts to ensure the trading goes there way (see FTC and QRK).   

I mean, I couldn't even get funds from the original developer.

Talk about ridiculous.

[sidhujag]

a couple other questions....

who administers the DVC distribution?

how do you actually get yourself in the distribution?

If your a bitcoin dev or can do devcoin dev than maybe ur on list for now..

alot of ppl forget we r eArly adopters fyi...

Are you on the list?   How did you get on the list?

I did the same work you did, but for IXC.

IXC had not been updated for 2 1/2 years.  So I made the effort to port it to the 0.8.6 code base.

However, I had to beg for funds here and I continue to have to beg for funds.

For some crazy reason, all these early adopters believe that they can do nothing and the the coin they bought would magically rise in value.   Well,  there are other coins out there that have more aggressive development and marketing budgets.   Some even focus their efforts to ensure the trading goes there way (see FTC and QRK).   

I mean, I couldn't even get funds from the original developer.

Talk about ridiculous.

Im not on list and well by def u should be i think.. if you can dev for devcoin..

Supposidely if u dev for bitcoin ur on the list.

[meta.p02]

I downloaded the devcoin client in the OP.

Overall, it seems okay so far (indexing the ~118K blocks will take much more time). However, there are some minor cosmetic errors:

1. The taskbar logo, the window icon and the "About Devcoin" logo are I0Coin.
2. In "Sign/Verify Message", the "Devcoin addresses" are actually I0Coin addresses.
3. "Pay To" says "Enter a Bitcoin address".

Other than that, I don't see any major problems. I'll wait further until the reindex is complete to update this post.

I had to restart the client after reindex was completed to get the new blocks to show up. Other than that, things seem to be working fine.

Code:

18:28:44

getinfo


18:28:45

{
"version" : 80501,
"protocolversion" : 70001,
"walletversion" : 10500,
"balance" : 45000.00000000,
"blocks" : 118801,
"timeoffset" : 2,
"connections" : 8,
"proxy" : "",
"difficulty" : 468145620.50036091,
"testnet" : false,
"keypoololdest" : 1378797514,
"keypoolsize" : 101,
"paytxfee" : 1.00000000,
"errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"
}

Code:

Memory usage
New: 59.6 MB
Old: 224.1 MB

[rsnel]

@FrictionLessCoin & @sidhujag

I'm glad you two took the task of upgrading DVC and IXC.

Small remark about generating binaries, for I0coin I use the official bitcoin-way of building, documented in 'release-process.md'.

[Wekkel]

Tested the Windows client on Windows 8.1 64 bit.

It works fine, downloads the missing blocks and is able to receive DVC. Will try sending coins later after which I will make a small post at Devtome about this beta client.

I understand it will have an installer when ready?

[FrictionlessCoin]

@FrictionLessCoin & @sidhujag

I'm glad you two took the task of upgrading DVC and IXC.

Small remark about generating binaries, for I0coin I use the official bitcoin-way of building, documented in 'release-process.md'.

I did not do the DVC port.

But anyway,  let me read the bitcoin-way.   Thanks for the heads up.   

We definitely want from iXcoin a very well structured process for releasing code.   Right now its a bit haphazard.

[emfox]

Does your src exactly based on bitcoin 0.8.5 ? I see some files missing, e.g. src/leveldb/Makefile is in bitcoin 0.8.5, but not in your devcoin source, and that prevent me from build on linux.

Edit: after add src/leveldb/Makefile from original bitcoin 0.8.5, and add line '-l curl' in LIBS in makefile.unix, I could build devcoind properly on my debian box.

I suggest change the captical D to d, 'cause it not so normal that we use $HOME/.Devcoin and Devcoin.conf file.

[Wekkel]

Ok, tested the Windows client on Windows 8.1 64 bit. Sending and receiving coins works. Screenshots here.

[sidhujag]

Does your src exactly based on bitcoin 0.8.5 ? I see some files missing, e.g. src/leveldb/Makefile is in bitcoin 0.8.5, but not in your devcoin source, and that prevent me from build on linux.

Edit: after add src/leveldb/Makefile from original bitcoin 0.8.5, and add line '-l curl' in LIBS in makefile.unix, I could build devcoind properly on my debian box.

I suggest change the captical D to d, 'cause it not so normal that we use $HOME/.Devcoin and Devcoin.conf file.

Taken from i0coin which was based on btc 0.8.5... I can add that makefile I will get it from 0.8.5 thanks...

Once you can build please share the makefile so I can update it. We are still testing so the official binaries will come after we are done testing. But can I rely on you to make the linux builds? Can you do 64 and 32 bit?

About the lowercase 'd' thing... fixed in 1.0.1, can you retest for this?

Thanks
Jag

[sidhujag]

@FrictionLessCoin & @sidhujag

I'm glad you two took the task of upgrading DVC and IXC.

Small remark about generating binaries, for I0coin I use the official bitcoin-way of building, documented in 'release-process.md'.

I did not do the DVC port.

But anyway,  let me read the bitcoin-way.   Thanks for the heads up.   

We definitely want from iXcoin a very well structured process for releasing code.   Right now its a bit haphazard.

I agree, I did not look at the bitcoin way because I think it wouldn't build devcoin (different naming) and more dependencies were added like libcurl etc so for now its a manual process until we figure out how to make it work for official builds which would be a nice - to - have.

[sidhujag]

user weisoq sent me: "On your new build, not sure if fees are working correctly. I sent wekkel 10 dvc to test his install (which subtracts the flat 1dvc from my balance, so 11 dvc sent). He seems to have sent me back 10, but I've received 9.5 (so I assume the client has subtacted the fee from the send amount rather than balance, and not sure why it's 0.5 dvc rather than 1?)

It may have something to do with those 10dvc being the only coins in his new wallet, but even then why 0.5, so thought you might want to check."

 noticed that in the official repository for the old devcoin that GetMinFee doesn't uncomment the section where fAllowFree resets the fee's for transactions less than 27k coins. However on the wiki http://www.devtome.com/doku.php?id=devcoin where UnthinkingBit wrote that GetMinFee() was changed by removing the fAllowFree code... this doesn't actually exist in the official source... however I did just make this change so please retest the transactions.

I updated the binaries to v1.0.1.. its a manual process until we can actually figure out how to use the proper release process (which we are not ready for yet anyway until testing is complete)...

[Wekkel]

user weisoq sent me: "On your new build, not sure if fees are working correctly. I sent wekkel 10 dvc to test his install (which subtracts the flat 1dvc from my balance, so 11 dvc sent). He seems to have sent me back 10, but I've received 9.5 (so I assume the client has subtacted the fee from the send amount rather than balance, and not sure why it's 0.5 dvc rather than 1?)

It may have something to do with those 10dvc being the only coins in his new wallet, but even then why 0.5, so thought you might want to check."

I got 10 DVC from you and had no other balance. I have no voluntary payment fee configured for the client. The client demanded a minimum 0.5 DVC fee for the return payment. Hence, 9.5 DVC available and 0.5 as payment fee. See details of the payment here

[sidhujag]

user weisoq sent me: "On your new build, not sure if fees are working correctly. I sent wekkel 10 dvc to test his install (which subtracts the flat 1dvc from my balance, so 11 dvc sent). He seems to have sent me back 10, but I've received 9.5 (so I assume the client has subtacted the fee from the send amount rather than balance, and not sure why it's 0.5 dvc rather than 1?)

It may have something to do with those 10dvc being the only coins in his new wallet, but even then why 0.5, so thought you might want to check."

I got 10 DVC from you and had no other balance. I have no voluntary payment fee configured for the client. The client demanded a minimum 0.5 DVC fee for the return payment. Hence, 9.5 DVC available and 0.5 as payment fee. See details of the payment here

Well either way for tx amount above 27k we would never see an issue, but I think tx's below that may not have been right according to the wiki... so I commented out the fAllowFree code which resets fee's for transactions below 27000 coins, so fees aren't reset back to 0 now...

Let's try it again and make sure its right according tot he original spec.

[weisoq]

user weisoq sent me: "On your new build, not sure if fees are working correctly. I sent wekkel 10 dvc to test his install (which subtracts the flat 1dvc from my balance, so 11 dvc sent). He seems to have sent me back 10, but I've received 9.5 (so I assume the client has subtacted the fee from the send amount rather than balance, and not sure why it's 0.5 dvc rather than 1?)

It may have something to do with those 10dvc being the only coins in his new wallet, but even then why 0.5, so thought you might want to check."

I got 10 DVC from you and had no other balance. I have no voluntary payment fee configured for the client. The client demanded a minimum 0.5 DVC fee for the return payment. Hence, 9.5 DVC available and 0.5 as payment fee. See details of the payment here

Just about the test wekkel, not the dvc. It should have said something like 'you don't have the funds, change the send amount'. Let me know when you have the newest update and I'll try sending again.

[sidhujag]

user weisoq sent me: "On your new build, not sure if fees are working correctly. I sent wekkel 10 dvc to test his install (which subtracts the flat 1dvc from my balance, so 11 dvc sent). He seems to have sent me back 10, but I've received 9.5 (so I assume the client has subtacted the fee from the send amount rather than balance, and not sure why it's 0.5 dvc rather than 1?)

It may have something to do with those 10dvc being the only coins in his new wallet, but even then why 0.5, so thought you might want to check."

I got 10 DVC from you and had no other balance. I have no voluntary payment fee configured for the client. The client demanded a minimum 0.5 DVC fee for the return payment. Hence, 9.5 DVC available and 0.5 as payment fee. See details of the payment here

Just about the test wekkel, not the dvc. It should have said something like 'you don't have the funds, change the send amount'. Let me know when you have the newest update and I'll try sending again.

Ok I uploaded 1.0.1 for the qt binary you can try it again. I don't know if it will throw up a message saying you don't have enough or whatever but as long as the fee's are "right" I think its good for now.

Thanks,
Jag

[sidhujag]

I downloaded the devcoin client in the OP.

Overall, it seems okay so far (indexing the ~118K blocks will take much more time). However, there are some minor cosmetic errors:

1. The taskbar logo, the window icon and the "About Devcoin" logo are I0Coin.
2. In "Sign/Verify Message", the "Devcoin addresses" are actually I0Coin addresses.
3. "Pay To" says "Enter a Bitcoin address".

Other than that, I don't see any major problems. I'll wait further until the reindex is complete to update this post.

Fixed points 2 and 3 in 1.0.1, thanks.

For point 1 we will have a bounty of I think 8 shares for the new qt images and 4 shares for second best... the images we need are in the  original post of this thread.

[markm]

The main purpose of fees is to discourage spamming.

Devcoin creates (more than) 1000 times as many coins per block as bitcoin so fees were set as a thousand times higher than bitcoin's fees back when we created Devcoin.

The idea was that Devcoins would be worth 1/1000 (at best, and actually now that bitcoin makes only 25 coins not 50, presumably more like 1/2000) of what bitcoins are worth, so that however many bitcoins of fee it would take to discourage spammers it would presumably take 1000 (nowadays maybe more like at least 2000) times as much fee to accomplish the same amount of discouragement in Devcoin.

So maybe while you are at it you should update our old "fees 1000 times as much as bitcoin's fees" to be at least 2000 times as much.

Which would be a hard fork, so should be set to come into effect at some particular block number.

Plus we can predict ahead too, we know in how many years bitcoin will again halve its number of coins per block, so maybe we could plan ahead to have our fees jump yet again at those times. Though when those times actually come bitcoin will maybe have changed its fees so come the day we'd want to look at bitcoin's fees and do our multiply accordingly then when updating devcoin again then.

-MarkM-