Devcoin - page 65. | Bitcointalksearch.org

twobits

sr. member

Activity: 574

Merit: 250

Quote from: FuzzyBear on May 05, 2013, 04:04:38 PM

has anyone proposed this to friedcat? that they mine on bitparking some of their hashing power... are they? bitparking saw mass increase not to long ago...from 1TH to like 4-5 now?

People have posted suggesting mm in their thread.

They are also starting to mine on bitminter now, so presumably getting nmc.

Personally I am glad that I can still mine some of the other coins and they are not yet.

FuzzyBear

legendary

Activity: 1420

Merit: 1010

Quote from: markm on May 05, 2013, 03:53:42 PM

How many shares would we need in order to propose a motion that ASICMiner merge DeVCoins into their mining?

Shareholders should already anyway be complaining that ASICMiner is not merging an optimum number of chains into its mining, it is failing in its duty to shareholders of producing maximum earnings with its equipment!

Are we to support an operation that is so lax in its duties?

-MarkM-

has anyone proposed this to friedcat? that they mine on bitparking some of their hashing power... are they? bitparking saw mass increase not to long ago...from 1TH to like 4-5 now?

markm

legendary

Activity: 2940

Merit: 1090

How many shares would we need in order to propose a motion that ASICMiner merge DeVCoins into their mining?

Shareholders should already anyway be complaining that ASICMiner is not merging an optimum number of chains into its mining, it is failing in its duty to shareholders of producing maximum earnings with its equipment!

Are we to support an operation that is so lax in its duties?

-MarkM-

FuzzyBear

legendary

Activity: 1420

Merit: 1010

There is a new listing on cryptostocks - ASCMDVCPT

https://cryptostocks.com/securities/39

This has been setup by user twobits, so I think he is entitled to the business bounty if he sells $1 worth of stock? unthinkingbit?

I have created a thread at his request to help answer some questions relating to the investment so he can carry on doing the good programming that he has been doing of late

so please post any questions here:
https://bitcointalksearch.org/topic/closed-dvc-ascmdvcpt-cryptostock-investment-196217

Please show your support fellow devcoin users and this is a great opportunity as I see to invest in ASICMiner shares and help boost devcoin value with the buying of devcoins from dividends paid out by the ASICMiner shares

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: markm on May 05, 2013, 09:07:08 AM

I have built devcoind with the new reciever.h

Moved ~/.devcoin/receiver to ~/.devcoin/receiver.gone

Now to see if it does in fact bootstrap itself up without needing me to manually provide it with the receivers files or directory...

(Will edit with results soon, currently it is just opening its wallet / scanning blockchain...)

...Okay, it created a new receiver directory and populated it! Cool.

Update pushed to github at:

https://github.com/knotwork/old-devcoind

https://github.com/knotwork/old-devcoin-qt

-MarkM-

should i create a new bundle? its not really neccessary.
also did someone create a installer yet?

FinShaggy

full member

Activity: 196

Merit: 100

Google/YouTube

CHECK OUT THE NEW DEVCOIN FORUMS

http://homegrownsouth.com/forum/viewforum.php?f=14

shadypepe

sr. member

Activity: 266

Merit: 250

thinking about it, what about a futures market for dvc? the system is basically predestined for it because somebody knows for sure he/she will get paid in a months time but maybe needs money today. buyers of a long futures contract wouldn't even have to trust the other party because they can look it up when and how much they will receive. also i guess it would bring certainty/stability to the price

psybits

legendary

Activity: 1386

Merit: 1000

I have been struggling with installing Devcoin on windows and just wanted to say that Twobits' installer is just great. Just how it should be

markm

legendary

Activity: 2940

Merit: 1090

I have built devcoind with the new reciever.h

Moved ~/.devcoin/receiver to ~/.devcoin/receiver.gone

Now to see if it does in fact bootstrap itself up without needing me to manually provide it with the receivers files or directory...

(Will edit with results soon, currently it is just opening its wallet / scanning blockchain...)

...Okay, it created a new receiver directory and populated it! Cool.

Update pushed to github at:

https://github.com/knotwork/old-devcoind

https://github.com/knotwork/old-devcoin-qt

-MarkM-

twobits

sr. member

Activity: 574

Merit: 250

Quote from: Unthinkingbit on May 05, 2013, 03:10:03 AM

The current client can not handle spaces in the path, the next version should and hopefully it will be ready in a few weeks. You could try manually making a folder called 'receiver' in your .devcoin folder and copying all the receiver files into that. If that doesn't work, you could try putting the receiver files into the same folder which contains the devcoin executable.

Maybe the first post can be updated to point to the builds at https://www.box.com/s/1mqfk22gyqq97ytdmifi ? I think they do help with the bootstrapping issues many see.

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Quote from: markm on May 05, 2013, 06:01:02 AM

Does the new receiver.h have this fix for spaces in paths?

Yup, the receiver.h which Twobits made has the change:

Quote

232c234
< string directoryPath = (filesystem::path(fileName)).parent_path().string();
---
> string directoryPath = getReplaced((filesystem::path(fileName)).parent_path().string());

markm

legendary

Activity: 2940

Merit: 1090

Does the new receiver.h have this fix for spaces in paths?

-MarkM-

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Quote from: markm on May 04, 2013, 10:33:35 PM

..
Apparently it either does not have write permission to write the file or the space in the path is making it maybe even think the directory it is to write the file to does not exist.

The current client can not handle spaces in the path, the next version should and hopefully it will be ready in a few weeks. You could try manually making a folder called 'receiver' in your .devcoin folder and copying all the receiver files into that. If that doesn't work, you could try putting the receiver files into the same folder which contains the devcoin executable.

markm

legendary

Activity: 2940

Merit: 1090

By receiver.cav it mean receiver_19.csv in this case. receiver.csv is just the base filename that the round number gets put into to name a specific instance of such files.

Apparently it either does not have write permission to write the file or the space in the path is making it maybe even think the directory it is to write the file to does not exist.

-MarkM-

grc

newbie

Activity: 40

Merit: 0

Quote from: markm on May 04, 2013, 10:25:53 AM

It picks a random lbock number at which to go get next set of receiver files, I think it would have been round 19 it would have already got before reaching block 76000, then sometime before block 8000 it would try to get round 20. Possibly block 76221 is the random block number at which it decided to do that.

Is the receivers list number 20 in the receiver subdirectory of the data directory?

Extra copies of receiver files lying around elsewhere it likely will not even be seeing, unless by change they happen to be in the directrory that was the program's "current working directory" when it was run. (In which case it should have copied them to the receiver directory of the data directory).

I guess with all the flavours of coins though there is always the weird times when people seem to end up deleting the blockchain and re-getting it from scratch. Hate to blindly try that without knowing the actual problem though.

Is there any clue in the debug.log file that is in the data directrory?

Does it write something to console maybe about files it got being identical or not?

Does it actually have connections? It is not some old version is it?

-MarkM-

Thanks for the help.

Devcoin didn't ever create a receiver directory in ~/Library/Application Support/Devcoin, although it did create an empty receiver directory in ~/Library/ApplicationSupport/Devcoin (missing a space). Is there any chance that devcoin can't handle spaces in the path to the receiver files?

I noticed lots of these messages towards the beginning of the log, but none have come up recently:

Code:

The file /Users/grc/Library/Application Support/Devcoin/receiver/receiver_19.csv can not be written to.
Warning, no coin lists were found for the file: receiver.csv

Is there meant to be a receiver.csv file? There are also thousands of 'got inventory: block _ have' messages in the log.

I have about 8 connections at the moment. The client looks old, but I haven't been able to find any newer devcoin clients. I think I got it here.

I'm happy to just download the blockchain again as long as I won't lose my address. Which files should I delete?

FinShaggy

full member

Activity: 196

Merit: 100

Google/YouTube

If anyone wants to join a forum that has a section specifically for Devcoin, come over here

:
http://homegrownsouth.com/forum/viewforum.php?f=19

rekuku

newbie

Activity: 18

Merit: 0

LOL

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Leojane:
http://devtome.com/doku.php?id=wiki:user:leojane

has written more than a thousand words:
http://devtome.com/doku.php?id=cyprus_and_cryptocurrencies

and so got the ninth, two generation share signing bonus for writing:
http://www.devtome.com/doku.php?id=earn_devcoins_by_writing#signing_bonus

There is now one, two share bonus remaining. The writer will also get earnings per word:
http://www.devtome.com/doku.php?id=earn_devcoins_by_writing#earnings_per_word

shadypepe

sr. member

Activity: 266

Merit: 250

ok thanks for clarifying! i tried to understand it from the documentation but your explanation helped me more Wink

metazilla

member

Activity: 75

Merit: 10

Quote from: shadypepe on May 04, 2013, 03:16:35 PM

so the shares from last round are going to be paid out evenly across the whole round and the signing bonusses are integrated in that? can somebody confirm this please?

The shares from round 22 will be paid out in the blocks 88000-91999. Each block pays out 50000 coins, 45000 of which go to generation shares (the other 5000 go to miners). The devtome page on Devcoin has more detailed info, but basically how it works is the list of addresses in the receiver file are paid out one at a time. I'm not sure if it's possible to predict exactly which blocks you will be paid out. But say you had 10 shares, and there were 100 shares, you'd expect to be paid every 10 blocks. Note that you will not receive the entirety of your shares until the last block (~92000), which I estimate (based on an average block time of 10min) will happen around the end of May.

More technical info here: http://www.devtome.com/doku.php?id=devcoin#receiver_files

Topic: Devcoin - page 65. (Read 412952 times)