What is the reason that all these receiver files are stored externally? Would it not be possible to store them directly in the block chain?
There was a method to do this with the bitcoin blockchain (see here: https://bitcointalksearch.org/topic/announce-bitcoin-message-service-v10-within-block-chain-47283) and it seems to be a problem already solved by Namecoin (you can link 1023 bytes of data to a certain name).
It seems like getting all of these receiver files is big stumbling block for setting up the Devcoin wallet (I gave up setting mine after a few attempts, and just made one on devda.ch), and ideally it seems like it'd be better to have a solution that isn't dependent on people hosting the files.
Thoughts?
Topic: Devcoin - page 98. (Read 412952 times)
BTW, the windows bounty for an installer is for the wrong thing. The bootstrapping issue is currently in all three platforms, not just windows. I should have something working in a day or so. Anyone want to test, if so pm me, and for what platform(s).
Ok. at this point I have made some changes that can allow a fresh install to bootstrap itself, with no receiver_ files.
However it is fragile.. for example, earlier today I was getting https://www.box.com/s/3v8jahr8ge29dcfjvomb as the receive_0.csv from the github url. I have not yet been able to determine what http status code github is giving when
this happens, nor can I get it to happen often enough to catch it with the command line curl yet. If anyone can capture
that status headers for this result it would help. The code current can never recover once this happens. It also has other
points that it will either never recover or 'attack' the host by trying to fetch the url many times a second when things fail
to fetch cleanly the first time. There is also an odd bug that a space in the path to the receiver files gets stripped when
the directory is first made, but not later when it tries to write to that locations, so it then fails again. What I have works much better then what the current release does but it still needs more error recovery and robustness... however no ones is interested anyway, I got zero replies or pms and people are more interested in writing and banners it seems then a sound fundamental client.
I any case the code I have fails still in odd ways, but regression testing shows the original code failed the same way as well, so I am pretty sure what I have is better but still not great
Edit: To see what is in the csv file, download it and rename it to end in .html and load it in your browser.
Basically it is a fail that says "This page is taking way too long to load.
Sorry about that. Please try refreshing and contact us if the problem persists."
I've made a design for possible buttons following the style of my logo proposal.
I prefer the negative version (the first option). Here is in high res: https://i.imgur.com/KMUG4O0.png
Do you like them?
I prefer the negative version (the first option). Here is in high res: https://i.imgur.com/KMUG4O0.png
Do you like them?
Marticps is awarded the second 3/5 share button bounty:
https://bitcointalksearch.org/topic/m.1450786
There is now one 3/5 share award remaining.
lots of action with Devcoin right now, how come?
maybe fontas is preparing a pump...
GPL ECA Reactor image published.
EAW Concentrate avalable for DVC
https://bitcointalksearch.org/topic/m.1929617
Here is the challange to get the data published trough DVB:
1M DVB Shares a 250 DVC each are issued.
When all 250 priced DVB shares are sold before the 1000 ECA shares a 0.5 BTC- the data on defcad.org will reference to Devcoin.
The gained funds will be used for 3D printing equipment aquisition.
EAW Concentrate avalable for DVC
https://bitcointalksearch.org/topic/m.1929617
Here is the challange to get the data published trough DVB:
1M DVB Shares a 250 DVC each are issued.
When all 250 priced DVB shares are sold before the 1000 ECA shares a 0.5 BTC- the data on defcad.org will reference to Devcoin.
The gained funds will be used for 3D printing equipment aquisition.
lots of action with Devcoin right now, how come?
Hi, I have a clarifying question about earning coins by writing for the wiki. I just submitted an article (http://www.devtome.com/doku.php?id=meditation) that was over a thousand words, but I still don't think I'm entirely finished with it. Say I get rewarded for the words I wrote, but later I want to add to the article, can I still get rewarded for later additions? Also, what about contributing to articles others have written, how would the rewards work in this case (or is editing others' articles not allowed)?
Yes, if you add additional words to an article you have already written later on, you will be paid for those additional words automatically in the next months generation shares, when the script is run to calculate and generate the generation share payouts.
As far as I know, if you add words to someone elses article is between you and the author, to arrange for you to receive some of the authors generation shares. Someone feel free to correct me if I am wrong!
Thank you for the clarification. I just did not want to go through all 79 pages right now, as I was sure the question had already been answered previously.
Hi, I have a clarifying question about earning coins by writing for the wiki. I just submitted an article (http://www.devtome.com/doku.php?id=meditation) that was over a thousand words, but I still don't think I'm entirely finished with it. Say I get rewarded for the words I wrote, but later I want to add to the article, can I still get rewarded for later additions? Also, what about contributing to articles others have written, how would the rewards work in this case (or is editing others' articles not allowed)?
Yes, if you add additional words to an article you have already written later on, you will be paid for those additional words automatically in the next months generation shares, when the script is run to calculate and generate the generation share payouts.
As far as I know, if you add words to someone elses article is between you and the author, to arrange for you to receive some of the authors generation shares. Someone feel free to correct me if I am wrong!
Now that I am finally free from the Newbies section;
I am a publisher on Devtome and have earned my signing bonus, but I have a question.
Lets say that an article I am writing is a WIP, such as my Sigmund Freud article, Lets say I save it at 1200 words
And then the python script runs for word count for payment, I get paid for the 1200 words.
I go back and add more to it, lets say I add an additional 5000 words, do the added words get accepted for payment of the next round? Or is all lost after the initial script run?
I am a publisher on Devtome and have earned my signing bonus, but I have a question.
Lets say that an article I am writing is a WIP, such as my Sigmund Freud article, Lets say I save it at 1200 words
And then the python script runs for word count for payment, I get paid for the 1200 words.
I go back and add more to it, lets say I add an additional 5000 words, do the added words get accepted for payment of the next round? Or is all lost after the initial script run?
You could work out how many bitcoins each share was worth in the past rounds, but the more effective this marketing is the less predictable the number of shares per round going forward will be, so do not put "forward-looking statements" into the marketing. Just show them how much writers have made in the past. Likely they will make less devcoins per share going forward but depending on how exchange rates go that might or might not work out to less bitcoins which in turn might or might not work out to less dollars...
-MarkM-
-MarkM-
I agree, please do not tell people how many devcoins there will be in a generation share. As devcoin gets more popular, the value goes up and more generation shares are earned, meaning fewer devcoins per share. However, the value per share varies less because the increase in value counters the decrease in devcoins per share. Lately, the value of a generation share has been around 200$, and it is likely to be over 150$ in the near future:
http://www.devtome.com/doku.php?id=earn_devcoins_by_writing#generation_share
I'm auctioning off a batch of 12 million devcoins: https://bitcointalksearch.org/topic/12-million-devcoins-48-hour-auction-185897
You could work out how many bitcoins each share was worth in the past rounds, but the more effective this marketing is the less predictable the number of shares per round going forward will be, so do not put "forward-looking statements" into the marketing. Just show them how much writers have made in the past. Likely they will make less devcoins per share going forward but depending on how exchange rates go that might or might not work out to less bitcoins which in turn might or might not work out to less dollars...
-MarkM-
-MarkM-
After re-reading that post I quoted, it looks like I made a mistake. It sounds like writing work will continue being added to the round 23 shares until block 89000, but currently we're actually still in round 21 - round 22 starts at 88000, and round 23 will start at 92000. So writers getting paid for round 23 should start getting paid in 5272 blocks, which at the current rate will be 39 days from now, which by my calculations is June 1st. At that point each block mined will pay out 45000 DVC to one of the people receiving shares. So basically the 4000 blocks from 92000-96000 will each pay 45000 DVC, split up equally among the shares, for a total of 180,000,000 DVC.
Based on the receiver files unthinkingbit posted a few pages back, I'm estimating that there are about 70 shares so far, with about 2.6 million DVC per share. At current exchange rate at Vircurex, that's about 5.66 BTC per share, at a value of about 763 USD! (Can someone check my math here?? Seems too good to be true.)
Which brings up an idea I had: I think if the potential earnings for writing were more obvious (imagine if you had a banner that was said Earn devcoins for writing 1000 words, $700 value!) we'd get a lot more writers. Could I propose a bounty for some sort of page that calculates the current number of shares based on the receiver files, estimates how many DVC each contributer will receive, the value of those DVC in BTC and USD, and the expected payout dates?
Based on the receiver files unthinkingbit posted a few pages back, I'm estimating that there are about 70 shares so far, with about 2.6 million DVC per share. At current exchange rate at Vircurex, that's about 5.66 BTC per share, at a value of about 763 USD! (Can someone check my math here?? Seems too good to be true.)
Which brings up an idea I had: I think if the potential earnings for writing were more obvious (imagine if you had a banner that was said Earn devcoins for writing 1000 words, $700 value!) we'd get a lot more writers. Could I propose a bounty for some sort of page that calculates the current number of shares based on the receiver files, estimates how many DVC each contributer will receive, the value of those DVC in BTC and USD, and the expected payout dates?
I am going to start advertising Devcoin and Devtome starting next round.
And once there are like 500 publishers and shares are like 100k each, Devcoins will start being worth a lot more. I see that happening around 3-8 months from the beginning of next round.
After re-reading that post I quoted, it looks like I made a mistake. It sounds like writing work will continue being added to the round 23 shares until block 89000, but currently we're actually still in round 21 - round 22 starts at 88000, and round 23 will start at 92000. So writers getting paid for round 23 should start getting paid in 5272 blocks, which at the current rate will be 39 days from now, which by my calculations is June 1st. At that point each block mined will pay out 45000 DVC to one of the people receiving shares. So basically the 4000 blocks from 92000-96000 will each pay 45000 DVC, split up equally among the shares, for a total of 180,000,000 DVC.
Based on the receiver files unthinkingbit posted a few pages back, I'm estimating that there are about 70 shares so far, with about 2.6 million DVC per share. At current exchange rate at Vircurex, that's about 5.66 BTC per share, at a value of about 763 USD! (Can someone check my math here?? Seems too good to be true.)
Which brings up an idea I had: I think if the potential earnings for writing were more obvious (imagine if you had a banner that was said Earn devcoins for writing 1000 words, $700 value!) we'd get a lot more writers. Could I propose a bounty for some sort of page that calculates the current number of shares based on the receiver files, estimates how many DVC each contributer will receive, the value of those DVC in BTC and USD, and the expected payout dates?
Based on the receiver files unthinkingbit posted a few pages back, I'm estimating that there are about 70 shares so far, with about 2.6 million DVC per share. At current exchange rate at Vircurex, that's about 5.66 BTC per share, at a value of about 763 USD! (Can someone check my math here?? Seems too good to be true.)
Which brings up an idea I had: I think if the potential earnings for writing were more obvious (imagine if you had a banner that was said Earn devcoins for writing 1000 words, $700 value!) we'd get a lot more writers. Could I propose a bounty for some sort of page that calculates the current number of shares based on the receiver files, estimates how many DVC each contributer will receive, the value of those DVC in BTC and USD, and the expected payout dates?
FinShaggy, check out this post from earlier in the thread (quoted below). It looks like round 23 will end at block 89,000. As of this post it looks like we're at block 86728, so that leaves 2272 blocks remaining. Based on my calculations, it takes 10.75 min on average to find a block (based on the time it took to mine blocks 85000-86000). Based on this, it should take about 17 days to get to block 89000 if mining continues at the same rate, so round 23 should end on May 10th. Hope this helps. 
To New Bounty Hunters,
I was asked in a message how often the generation shares will be paid, below is the answer.
Generation rounds are 4,000 blocks long, about a month:
http://devtome.com/doku.php?id=devcoin#viewing_disbursements
People who received coins for round 22, whether from bounties:
https://github.com/Unthinkingbit/charity/blob/master/bounty_22.csv
or devtome writer earnings, will get paid in round 22. Any work done after about block 85,000 and until block 89,000 will go into round 23. Round 22 starts at block 4,000 * 22 = 88,000. At the time of this writing, the block number is 82,867:
https://vps.vircurex.com/
At about 1,000 blocks per week, work until roughly April 9 will go into bounty 22. Payments for bounty 22 will be between block 88,000, which will start around April 30, until around May 30. If your devcoin address is on your machine, in May you'll see many 45,000 devcoin payments arriving from generation.
The number of receiver lines will only be known at block 85,000, when the writer earnings are generated and the receiver file is made. Assuming there are 60 receiver lines this round, each line will get a payment every 60 blocks, and on average each line will receive a total of 180,000,000 devcoins / 60 = 3,000,000 devcoins. For example, if someone made four generation shares from the signing bonus, and two for articles, for a total of six shares, they would get six payments every 60 rounds, or an average of a payment every 10 rounds. Their total payment would be on average 6 * 3,000,000 devcoins = 18,000,000 devcoins. Calculated at one payment every ten rounds, that gives the same figure of 4,000 / 10 * 45,000 devcoins = 18,000,000 devcoins.
I was asked in a message how often the generation shares will be paid, below is the answer.
Generation rounds are 4,000 blocks long, about a month:
http://devtome.com/doku.php?id=devcoin#viewing_disbursements
People who received coins for round 22, whether from bounties:
https://github.com/Unthinkingbit/charity/blob/master/bounty_22.csv
or devtome writer earnings, will get paid in round 22. Any work done after about block 85,000 and until block 89,000 will go into round 23. Round 22 starts at block 4,000 * 22 = 88,000. At the time of this writing, the block number is 82,867:
https://vps.vircurex.com/
At about 1,000 blocks per week, work until roughly April 9 will go into bounty 22. Payments for bounty 22 will be between block 88,000, which will start around April 30, until around May 30. If your devcoin address is on your machine, in May you'll see many 45,000 devcoin payments arriving from generation.
The number of receiver lines will only be known at block 85,000, when the writer earnings are generated and the receiver file is made. Assuming there are 60 receiver lines this round, each line will get a payment every 60 blocks, and on average each line will receive a total of 180,000,000 devcoins / 60 = 3,000,000 devcoins. For example, if someone made four generation shares from the signing bonus, and two for articles, for a total of six shares, they would get six payments every 60 rounds, or an average of a payment every 10 rounds. Their total payment would be on average 6 * 3,000,000 devcoins = 18,000,000 devcoins. Calculated at one payment every ten rounds, that gives the same figure of 4,000 / 10 * 45,000 devcoins = 18,000,000 devcoins.
Thank you
FinShaggy, check out this post from earlier in the thread (quoted below). It looks like round 23 will end at block 89,000. As of this post it looks like we're at block 86728, so that leaves 2272 blocks remaining. Based on my calculations, it takes 10.75 min on average to find a block (based on the time it took to mine blocks 85000-86000). Based on this, it should take about 17 days to get to block 89000 if mining continues at the same rate, so round 23 should end on May 10th. Hope this helps.
To New Bounty Hunters,
I was asked in a message how often the generation shares will be paid, below is the answer.
Generation rounds are 4,000 blocks long, about a month:
http://devtome.com/doku.php?id=devcoin#viewing_disbursements
People who received coins for round 22, whether from bounties:
https://github.com/Unthinkingbit/charity/blob/master/bounty_22.csv
or devtome writer earnings, will get paid in round 22. Any work done after about block 85,000 and until block 89,000 will go into round 23. Round 22 starts at block 4,000 * 22 = 88,000. At the time of this writing, the block number is 82,867:
https://vps.vircurex.com/
At about 1,000 blocks per week, work until roughly April 9 will go into bounty 22. Payments for bounty 22 will be between block 88,000, which will start around April 30, until around May 30. If your devcoin address is on your machine, in May you'll see many 45,000 devcoin payments arriving from generation.
The number of receiver lines will only be known at block 85,000, when the writer earnings are generated and the receiver file is made. Assuming there are 60 receiver lines this round, each line will get a payment every 60 blocks, and on average each line will receive a total of 180,000,000 devcoins / 60 = 3,000,000 devcoins. For example, if someone made four generation shares from the signing bonus, and two for articles, for a total of six shares, they would get six payments every 60 rounds, or an average of a payment every 10 rounds. Their total payment would be on average 6 * 3,000,000 devcoins = 18,000,000 devcoins. Calculated at one payment every ten rounds, that gives the same figure of 4,000 / 10 * 45,000 devcoins = 18,000,000 devcoins.
I was asked in a message how often the generation shares will be paid, below is the answer.
Generation rounds are 4,000 blocks long, about a month:
http://devtome.com/doku.php?id=devcoin#viewing_disbursements
People who received coins for round 22, whether from bounties:
https://github.com/Unthinkingbit/charity/blob/master/bounty_22.csv
or devtome writer earnings, will get paid in round 22. Any work done after about block 85,000 and until block 89,000 will go into round 23. Round 22 starts at block 4,000 * 22 = 88,000. At the time of this writing, the block number is 82,867:
https://vps.vircurex.com/
At about 1,000 blocks per week, work until roughly April 9 will go into bounty 22. Payments for bounty 22 will be between block 88,000, which will start around April 30, until around May 30. If your devcoin address is on your machine, in May you'll see many 45,000 devcoin payments arriving from generation.
The number of receiver lines will only be known at block 85,000, when the writer earnings are generated and the receiver file is made. Assuming there are 60 receiver lines this round, each line will get a payment every 60 blocks, and on average each line will receive a total of 180,000,000 devcoins / 60 = 3,000,000 devcoins. For example, if someone made four generation shares from the signing bonus, and two for articles, for a total of six shares, they would get six payments every 60 rounds, or an average of a payment every 10 rounds. Their total payment would be on average 6 * 3,000,000 devcoins = 18,000,000 devcoins. Calculated at one payment every ten rounds, that gives the same figure of 4,000 / 10 * 45,000 devcoins = 18,000,000 devcoins.
I've made a design for possible buttons following the style of my logo proposal.
I prefer the negative version (the first option). Here is in high res: https://i.imgur.com/KMUG4O0.png
Do you like them?
I prefer the negative version (the first option). Here is in high res: https://i.imgur.com/KMUG4O0.png
Do you like them?
Does anyone know how many blocks are left, I don't know how to tell.
Here are the stats from Vircurex:
Devcoin:
Blocks: 86721
Difficulty: 584,663.5314
Networks GH/s: 2,615.0140
Here are the stats from Vircurex:
Devcoin:
Blocks: 86721
Difficulty: 584,663.5314
Networks GH/s: 2,615.0140
I would like to request a bounty be discussed for a text populating wizard/flow that can be used as a standardized generator for security prospectus so more devcoin based securities can be issued on cryptostocks or other sites.
I suggest a 6 then 3 share bounty.
Are there any objections, or should anything be changed?
Requirements I can think of off the top of my head:
1. The generator must be capable of generating the information for a prospectus for each type of security.
2. There should be input fields to populate each of the items that would need changing on the wizard, such as % for dividends or operation fees and overhead.
Edit:
3. The text should be editable from the text fields as the information is populated.
Anyone else got ideas. I will think on this some more.
Are there some fallback nodes?
I have a dedicated server now so it should be running with port open at 198.154.60.183 hopefully 24/7 forever now.
At some point I will point a hostname at that server. I guess I should also look into how DNS seed works and set some up in the DNS of my knotwork.com domain and hey why not, some of the devtome/devcoin domains too if possible.
-MarkM-
That worked, thanks. Seems all of the seeds built into the client are now dead. Maybe we need some new 24/7 nodes? Let me know and I can look into setting one up.
BTW, the windows bounty for an installer is for the wrong thing. The bootstrapping issue is currently in all three platforms, not just windows. I should have something working in a day or so. Anyone want to test, if so pm me, and for what platform(s).
Jump to: