All you need is a daemon to do transactions. The GUI is just to make it easier for people to use
Doesn't the -qt lack some features present on the daemon?
Topic: [DVC]DevCoin - Official Thread - Moderated - page 342. (Read 1059181 times)
Doesn't the -qt lack some features present on the daemon?
Is DVB (on crypto stock, or it's verified real life person) somehow related with DevCoin's bounty system?
Not directly.
As far as I understand, the person behind it, Richard Porubcan, paid some bounties on behalf of DVB, and also he helped to organize some projects which got Devcoin bounties (shares).
i.e.: by buying DVBs, do we help the Community, or only help ourselves?
It's hard to say, DVB lacks clearly written policy.
Also, if not, is there some kind of bank/cooperative/fund/... that manages the actual bounties (not the shares) so we could finance this "fund", and reclaim our coins later (with or without interest...)?
I think this is what DVB was supposed to be about, but it isn't managed in a clear and transparent manner.
Perhaps you can start by describing how exactly it should work.
Hi
I have another noob (and perhaps stupid) question:
Is DVB (on crypto stock, or it's verified real life person) somehow related with DevCoin's bounty system?
i.e.: by buying DVBs, do we help the Community, or only help ourselves?
I've read all written about DVB here and on Devtome (nothing there!), and my preliminary conclusion is negative.
Please correct me, or direct me towards the right info...
Also, if not, is there some kind of bank/cooperative/fund/... that manages the actual bounties (not the shares) so we could finance this "fund", and reclaim our coins later (with or without interest...)?
Thanks in advance,
mrca
I have another noob (and perhaps stupid) question:
Is DVB (on crypto stock, or it's verified real life person) somehow related with DevCoin's bounty system?
i.e.: by buying DVBs, do we help the Community, or only help ourselves?
I've read all written about DVB here and on Devtome (nothing there!), and my preliminary conclusion is negative.
Please correct me, or direct me towards the right info...
Also, if not, is there some kind of bank/cooperative/fund/... that manages the actual bounties (not the shares) so we could finance this "fund", and reclaim our coins later (with or without interest...)?
Thanks in advance,
mrca
Wow. I'm surprised anyone could make a metal printer for that price. It's not a pure metal printer, because you have to burn off the binder in a kiln, but it's less work than the lost wax process, and a big step forward.
I could not find their email address, if someone can contact them and get them to post a devcoin address, I'll send them 6 million devcoins (currently around 500$) to start. In the article they mention they're using open source software, but they don't say if the printer design is open source. If it is, then we'll give them a big bounty in generation shares and I'll give them more of my own devcoins.
Note: An alternate way would be for someone to contribute a 1,000$ through their funding page:
https://www.indiegogo.com/projects/minimetalmaker-a-small-3d-printer-that-fabricates-with-precious-metal-clay/contributions/new?perk_amt=1000&perk_id=1498954
with their devcoin address in their name. Devcoins would be sent to that address, and that person would get an assembled MiniMetalMaker in Sep 2014, according to their posted schedule.
http://minimetalmaker.com/contactI could not find their email address, if someone can contact them and get them to post a devcoin address, I'll send them 6 million devcoins (currently around 500$) to start. In the article they mention they're using open source software, but they don't say if the printer design is open source. If it is, then we'll give them a big bounty in generation shares and I'll give them more of my own devcoins.
Note: An alternate way would be for someone to contribute a 1,000$ through their funding page:
https://www.indiegogo.com/projects/minimetalmaker-a-small-3d-printer-that-fabricates-with-precious-metal-clay/contributions/new?perk_amt=1000&perk_id=1498954
with their devcoin address in their name. Devcoins would be sent to that address, and that person would get an assembled MiniMetalMaker in Sep 2014, according to their posted schedule.
no email, but fb/twitter/funding platform contact links
[email protected]
Hi Guys,
Since right now the writers are being paid 90% generation I propose that we add in a bounty share funded by the generation. I thought this was the original purpose of the coin to fund developers and writing was just a result of devtome which was the result of a bounty completed by a developer? How did devtome end up hijacking the entire 90% of the coin generation? Anyways what makes sense is if there is incentive to do some bounties because that's what will bring about results. Devtome is a great project and as more people write the hope is that ad revenue will fully support the writers. Since it is on training-wheels still it needs some percentage of the coins being minted to still bring in more people to write. The original intent was that devtome would support itself and bounties would be an going process. I propose we stick to the plan and taper off the 90% of the writers earnings to something more reasonable. The bounty program is just as important if not more important to the success of the project than devtome (which is a single bounty project). Since training-wheels are still needed I propose 45% of the generation goes to writers and 45% goes to the bounty wallet (like a piggy bank) such that when it gets big enough there is enough incentive for it to be claimed to finish new projects.
I'm not sure how this was all lost and why the full generation has been going to devtome... seems like this was changed somewhere along the lines when devtome was introduced, but I propose we get back to a viable economic strategy here. Unless we want to be called devtomeCoin.
Admins/Developers need to vote yes or no and we can tally the results and publish them. Maybe with their vote they can include a short explanation for their vote.
Jag
Since right now the writers are being paid 90% generation I propose that we add in a bounty share funded by the generation. I thought this was the original purpose of the coin to fund developers and writing was just a result of devtome which was the result of a bounty completed by a developer? How did devtome end up hijacking the entire 90% of the coin generation? Anyways what makes sense is if there is incentive to do some bounties because that's what will bring about results. Devtome is a great project and as more people write the hope is that ad revenue will fully support the writers. Since it is on training-wheels still it needs some percentage of the coins being minted to still bring in more people to write. The original intent was that devtome would support itself and bounties would be an going process. I propose we stick to the plan and taper off the 90% of the writers earnings to something more reasonable. The bounty program is just as important if not more important to the success of the project than devtome (which is a single bounty project). Since training-wheels are still needed I propose 45% of the generation goes to writers and 45% goes to the bounty wallet (like a piggy bank) such that when it gets big enough there is enough incentive for it to be claimed to finish new projects.
I'm not sure how this was all lost and why the full generation has been going to devtome... seems like this was changed somewhere along the lines when devtome was introduced, but I propose we get back to a viable economic strategy here. Unless we want to be called devtomeCoin.
Admins/Developers need to vote yes or no and we can tally the results and publish them. Maybe with their vote they can include a short explanation for their vote.
Jag
I agree with the gist of this post, I think we should consider rearranging the shares and reallocating and vote yes.
Thanks,
To add to that I think we can get DVC onto the Tag Coin exchange which lets you trade bitcoin/tagcoins/devcoins? and deposit/withdraw up to 8 different fiat currencies. Fully regulated, 10 full time developers. I told the owner I'd like to add a Tag community in exchange to add DVC to his exchange. A Tag community certainly fits the marketing description for devcoin. We can eliminate the marketting shares from the list and associate a Tag Reward (affliative link) to each add and then reward based on number of signups or some other custom criteria. It really is a nice approach to deal with Pay per click spams. It raises the quality of ads aswell as people have incentive to draw more traffic to the ad if they get more coins based on signups. Ofcourse a certain % of the mining has to go to it but probably less than what we are using now. It can be dynamic based on number of signups last round.
Hi Guys,
Since right now the writers are being paid 90% generation I propose that we add in a bounty share funded by the generation. I thought this was the original purpose of the coin to fund developers and writing was just a result of devtome which was the result of a bounty completed by a developer? How did devtome end up hijacking the entire 90% of the coin generation? Anyways what makes sense is if there is incentive to do some bounties because that's what will bring about results. Devtome is a great project and as more people write the hope is that ad revenue will fully support the writers. Since it is on training-wheels still it needs some percentage of the coins being minted to still bring in more people to write. The original intent was that devtome would support itself and bounties would be an going process. I propose we stick to the plan and taper off the 90% of the writers earnings to something more reasonable. The bounty program is just as important if not more important to the success of the project than devtome (which is a single bounty project). Since training-wheels are still needed I propose 45% of the generation goes to writers and 45% goes to the bounty wallet (like a piggy bank) such that when it gets big enough there is enough incentive for it to be claimed to finish new projects.
I'm not sure how this was all lost and why the full generation has been going to devtome... seems like this was changed somewhere along the lines when devtome was introduced, but I propose we get back to a viable economic strategy here. Unless we want to be called devtomeCoin.
Admins/Developers need to vote yes or no and we can tally the results and publish them. Maybe with their vote they can include a short explanation for their vote.
Jag
Since right now the writers are being paid 90% generation I propose that we add in a bounty share funded by the generation. I thought this was the original purpose of the coin to fund developers and writing was just a result of devtome which was the result of a bounty completed by a developer? How did devtome end up hijacking the entire 90% of the coin generation? Anyways what makes sense is if there is incentive to do some bounties because that's what will bring about results. Devtome is a great project and as more people write the hope is that ad revenue will fully support the writers. Since it is on training-wheels still it needs some percentage of the coins being minted to still bring in more people to write. The original intent was that devtome would support itself and bounties would be an going process. I propose we stick to the plan and taper off the 90% of the writers earnings to something more reasonable. The bounty program is just as important if not more important to the success of the project than devtome (which is a single bounty project). Since training-wheels are still needed I propose 45% of the generation goes to writers and 45% goes to the bounty wallet (like a piggy bank) such that when it gets big enough there is enough incentive for it to be claimed to finish new projects.
I'm not sure how this was all lost and why the full generation has been going to devtome... seems like this was changed somewhere along the lines when devtome was introduced, but I propose we get back to a viable economic strategy here. Unless we want to be called devtomeCoin.
Admins/Developers need to vote yes or no and we can tally the results and publish them. Maybe with their vote they can include a short explanation for their vote.
Jag
I agree with the gist of this post, I think we should consider rearranging the shares and reallocating and vote yes.
Wow. I'm surprised anyone could make a metal printer for that price. It's not a pure metal printer, because you have to burn off the binder in a kiln, but it's less work than the lost wax process, and a big step forward.
I could not find their email address, if someone can contact them and get them to post a devcoin address, I'll send them 6 million devcoins (currently around 500$) to start. In the article they mention they're using open source software, but they don't say if the printer design is open source. If it is, then we'll give them a big bounty in generation shares and I'll give them more of my own devcoins.
Note: An alternate way would be for someone to contribute a 1,000$ through their funding page:
https://www.indiegogo.com/projects/minimetalmaker-a-small-3d-printer-that-fabricates-with-precious-metal-clay/contributions/new?perk_amt=1000&perk_id=1498954
with their devcoin address in their name. Devcoins would be sent to that address, and that person would get an assembled MiniMetalMaker in Sep 2014, according to their posted schedule.
http://minimetalmaker.com/contactI could not find their email address, if someone can contact them and get them to post a devcoin address, I'll send them 6 million devcoins (currently around 500$) to start. In the article they mention they're using open source software, but they don't say if the printer design is open source. If it is, then we'll give them a big bounty in generation shares and I'll give them more of my own devcoins.
Note: An alternate way would be for someone to contribute a 1,000$ through their funding page:
https://www.indiegogo.com/projects/minimetalmaker-a-small-3d-printer-that-fabricates-with-precious-metal-clay/contributions/new?perk_amt=1000&perk_id=1498954
with their devcoin address in their name. Devcoins would be sent to that address, and that person would get an assembled MiniMetalMaker in Sep 2014, according to their posted schedule.
no email, but fb/twitter/funding platform contact links
Less than $1000 for a 3D printer that prints metal: http://gigaom.com/2013/11/12/meet-the-mini-metal-maker-a-basic-sub-1000-3d-printer-that-prints-metal/
One of our goals was 3D printing metal wasn't it?
-MarkM-
One of our goals was 3D printing metal wasn't it?
-MarkM-
That's amazing.
Wow. I'm surprised anyone could make a metal printer for that price. It's not a pure metal printer, because you have to burn off the binder in a kiln, but it's less work than the lost wax process, and a big step forward.
I could not find their email address, if someone can contact them and get them to post a devcoin address, I'll send them 6 million devcoins (currently around 500$) to start. In the article they mention they're using open source software, but they don't say if the printer design is open source. If it is, then we'll give them a big bounty in generation shares and I'll give them more of my own devcoins.
Note: An alternate way would be for someone to contribute a 1,000$ through their funding page:
https://www.indiegogo.com/projects/minimetalmaker-a-small-3d-printer-that-fabricates-with-precious-metal-clay/contributions/new?perk_amt=1000&perk_id=1498954
with their devcoin address in their name. Devcoins would be sent to that address, and that person would get an assembled MiniMetalMaker in Sep 2014, according to their posted schedule.
Less than $1000 for a 3D printer that prints metal: http://gigaom.com/2013/11/12/meet-the-mini-metal-maker-a-basic-sub-1000-3d-printer-that-prints-metal/
One of our goals was 3D printing metal wasn't it?
-MarkM-
One of our goals was 3D printing metal wasn't it?
-MarkM-
That's amazing.
All you need is a daemon to do transactions. The GUI is just to make it easier for people to use
The GUI is spaghetti-code-entwined into the daemon.
Thus if you use the GUI, you just tell it to also act as a server, by setting server=1 in config or --server on commandline or something like that.
The daemon you don't need to tell it to act as a server, as that is all it does, it lacks all the spaghetti-code monstrousness of the interwined GUI-code.
It would have been lovely if Satoshi had coded a GUI as a totally distinct separate thing from the actual back end, but he didn't and trying to dis-entangle them is hard enough that doubtless some folk figured he actually had to entwine them to get the GUI to work nicely since a GUI that constantly knows the exact state of the back end has certain advantages. A mess of callbacks would be needed otherwise, or a whole lot of polling, and so on.
So basically you either run the GUI version or the daemon version. To get the RPC calls when running the GUI you tell the GUI you want server mode enabled, which basically means provide what the daemon does as well as providing the GUI.
The daemon also has a mode in which it merely acts as a communications interface to talk to the resident copy of the daemon. That is maybe confusing if you are used to having a separate control program to talk to your daemons. Apparently there is even now some talk about making that separation in bitcoin, so you'd run bitcoind and it'd go resident, then use bitcoinctl or ctlbitcoind or some such to talk to it. But right now e.g. devcoind is also its own control/communications program. Probably it would equally well talk to the GUI's server mode, so if you wanted from the commandline, a script etc to ask the GUI, that is in server mode, some info you'd go "devcoind getinfo" just like you would to ask the resident daemon some info.
-MarkM-
Does the daemon include a wallet? If so Id say to just usr resident version of the daemon and not gui.. making guis are hard to do properly so I dont hate satoshi for creating loosely coupled code but in genetal you want to keep your data layer stateless so Id rather use a headless server on an exchange if wallet functionality exists. Thus if you use the GUI, you just tell it to also act as a server, by setting server=1 in config or --server on commandline or something like that.
The daemon you don't need to tell it to act as a server, as that is all it does, it lacks all the spaghetti-code monstrousness of the interwined GUI-code.
It would have been lovely if Satoshi had coded a GUI as a totally distinct separate thing from the actual back end, but he didn't and trying to dis-entangle them is hard enough that doubtless some folk figured he actually had to entwine them to get the GUI to work nicely since a GUI that constantly knows the exact state of the back end has certain advantages. A mess of callbacks would be needed otherwise, or a whole lot of polling, and so on.
So basically you either run the GUI version or the daemon version. To get the RPC calls when running the GUI you tell the GUI you want server mode enabled, which basically means provide what the daemon does as well as providing the GUI.
The daemon also has a mode in which it merely acts as a communications interface to talk to the resident copy of the daemon. That is maybe confusing if you are used to having a separate control program to talk to your daemons. Apparently there is even now some talk about making that separation in bitcoin, so you'd run bitcoind and it'd go resident, then use bitcoinctl or ctlbitcoind or some such to talk to it. But right now e.g. devcoind is also its own control/communications program. Probably it would equally well talk to the GUI's server mode, so if you wanted from the commandline, a script etc to ask the GUI, that is in server mode, some info you'd go "devcoind getinfo" just like you would to ask the resident daemon some info.
-MarkM-
The GUI is spaghetti-code-entwined into the daemon.
Thus if you use the GUI, you just tell it to also act as a server, by setting server=1 in config or --server on commandline or something like that.
The daemon you don't need to tell it to act as a server, as that is all it does, it lacks all the spaghetti-code monstrousness of the interwined GUI-code.
It would have been lovely if Satoshi had coded a GUI as a totally distinct separate thing from the actual back end, but he didn't and trying to dis-entangle them is hard enough that doubtless some folk figured he actually had to entwine them to get the GUI to work nicely since a GUI that constantly knows the exact state of the back end has certain advantages. A mess of callbacks would be needed otherwise, or a whole lot of polling, and so on.
So basically you either run the GUI version or the daemon version. To get the RPC calls when running the GUI you tell the GUI you want server mode enabled, which basically means provide what the daemon does as well as providing the GUI.
The daemon also has a mode in which it merely acts as a communications interface to talk to the resident copy of the daemon. That is maybe confusing if you are used to having a separate control program to talk to your daemons. Apparently there is even now some talk about making that separation in bitcoin, so you'd run bitcoind and it'd go resident, then use bitcoinctl or ctlbitcoind or some such to talk to it. But right now e.g. devcoind is also its own control/communications program. Probably it would equally well talk to the GUI's server mode, so if you wanted from the commandline, a script etc to ask the GUI, that is in server mode, some info you'd go "devcoind getinfo" just like you would to ask the resident daemon some info.
-MarkM-
Thus if you use the GUI, you just tell it to also act as a server, by setting server=1 in config or --server on commandline or something like that.
The daemon you don't need to tell it to act as a server, as that is all it does, it lacks all the spaghetti-code monstrousness of the interwined GUI-code.
It would have been lovely if Satoshi had coded a GUI as a totally distinct separate thing from the actual back end, but he didn't and trying to dis-entangle them is hard enough that doubtless some folk figured he actually had to entwine them to get the GUI to work nicely since a GUI that constantly knows the exact state of the back end has certain advantages. A mess of callbacks would be needed otherwise, or a whole lot of polling, and so on.
So basically you either run the GUI version or the daemon version. To get the RPC calls when running the GUI you tell the GUI you want server mode enabled, which basically means provide what the daemon does as well as providing the GUI.
The daemon also has a mode in which it merely acts as a communications interface to talk to the resident copy of the daemon. That is maybe confusing if you are used to having a separate control program to talk to your daemons. Apparently there is even now some talk about making that separation in bitcoin, so you'd run bitcoind and it'd go resident, then use bitcoinctl or ctlbitcoind or some such to talk to it. But right now e.g. devcoind is also its own control/communications program. Probably it would equally well talk to the GUI's server mode, so if you wanted from the commandline, a script etc to ask the GUI, that is in server mode, some info you'd go "devcoind getinfo" just like you would to ask the resident daemon some info.
-MarkM-
Certainly it could take hours. Quite a few hours.
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
This is what I see from my client:
https://www.dropbox.com/s/iiyawm8h77nogdf/Screenshot%202013-11-13%2007.21.36.png
On dvcstable01, getinfo says "blocks" : 113658 so maybe you aren't quite caught up yet?
(Your image says 105341 down at the bottom... that would be a couple of months or so ago...)
-MarkM-
Im in talks with adding dvc to a potentially very high volume exchange its new and they are setting it up but they need to be able to talk via json rpc with php to the daemon.. Im assuming its this:
http://www.devtome.com/doku.php?id=communicating_with_devcon_wallet_using_php
Also I hope we can vote on something so we can actually start with some bounties. I spoke to Unthinkingbit and he said management of the bounties has always been a problem so we need a way to allocate people to bounties and managers and developers. Management would get say 15% of the
bounty stake.
I truly think once we get back to the initial goals we will lift off. Writers will make more than today if price is above 40 sat's
Less than $1000 for a 3D printer that prints metal: http://gigaom.com/2013/11/12/meet-the-mini-metal-maker-a-basic-sub-1000-3d-printer-that-prints-metal/
One of our goals was 3D printing metal wasn't it?
-MarkM-
One of our goals was 3D printing metal wasn't it?
-MarkM-
We could have 3D printing designs paid for by Devtome. Number of downloads of your design = number of DVC shares.
Who would fund upfront cost to build?
Yea markm it was a goal so now we can buy it and
create designs.. how would we fund it when devtome takes up all the coins?
On dvcstable01, getinfo says "blocks" : 113658 so maybe you aren't quite caught up yet?
(Your image says 105341 down at the bottom... that would be a couple of months or so ago...)
(Your image says 105341 down at the bottom... that would be a couple of months or so ago...)
Oh I see. This is due to my own misunderstanding. When I started playing with Bitcoins I downloaded both Bitcoin/QT and MultiBit (the wallet software). When I used MultiBit, any transaction would have been instantaneous, no need to download the blockchain. I assumed that this was the way the protocol worked: you download the blockchain if you want to be part of the network but transactions to your wallet will be received right away, with no need to download the blockchain.
Now I understand that if you use the main client (such as the one for Devcoins), you need to download the whole blockchain to see the recent transactions, including the ones concerning your wallet.
Thanks!
Certainly it could take hours. Quite a few hours.
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
This is what I see from my client:
https://www.dropbox.com/s/iiyawm8h77nogdf/Screenshot%202013-11-13%2007.21.36.png
On dvcstable01, getinfo says "blocks" : 113658 so maybe you aren't quite caught up yet?
(Your image says 105341 down at the bottom... that would be a couple of months or so ago...)
-MarkM-
Certainly it could take hours. Quite a few hours.
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
This is what I see from my client:
https://www.dropbox.com/s/iiyawm8h77nogdf/Screenshot%202013-11-13%2007.21.36.png
Markm Can you please help? 
Hover your mouse over the link to your article.
See that it says wiki:user ?
You need the colon in there, [[:pagename]] or something like that, to make the link point out of the user-pages section to the actual main articles section.
-MarkM-
Thank you again for the quick answer.
Hello Friends,
I am having some issues with my DVC wallet. Given that CEX recently started mining DVCs, I downloaded the DVC app for Mac and created my wallet. I tried to withdraw some DVCs from CEX, I gave them my address but I don't see the transaction and I don't see my coins in my wallet.
I also tried the DVC faucet and again, no coins and no transactions.
What could be the reason? These are the two addresses that I am using on the DVC Mac app.
1K3TJU7dT9sN2VwNDheFGHvbTGxo3MCWjh
1NAnWxsFwxzpjXL4GcAXhDSGR2HD5zZsTH
I am having some issues with my DVC wallet. Given that CEX recently started mining DVCs, I downloaded the DVC app for Mac and created my wallet. I tried to withdraw some DVCs from CEX, I gave them my address but I don't see the transaction and I don't see my coins in my wallet.
I also tried the DVC faucet and again, no coins and no transactions.
What could be the reason? These are the two addresses that I am using on the DVC Mac app.
1K3TJU7dT9sN2VwNDheFGHvbTGxo3MCWjh
1NAnWxsFwxzpjXL4GcAXhDSGR2HD5zZsTH
It is old code, even the new database the latest bitcoins etc use takes time to catch up to the blockchain.
Old code could take days to get the blockchain maybe, depending on your modem speed and the speed at which your processor can verify blocks.
Certainly it could take hours. Quite a few hours.
What block does your client say it is on? (Damn do GUI clients even tell you what block they are on? I don't use GUI clients...)
-MarkM-
Markm Can you please help?
Hover your mouse over the link to your article.
See that it says wiki:user ?
You need the colon in there, [[:pagename]] or something like that, to make the link point out of the user-pages section to the actual main articles section.
-MarkM-
Jump to: