Topic: [UNOFFICIAL] [VNL] Vanillacoin 0.4.1 | Instant ▱ Incentivized ▱ Innovative - page 91. (Read 433405 times)
September 25, 2015, 07:22:30 AM
Then it seems like I didn't get a single incentive reward in a week. How often are they? The votecandidate value is true.
September 25, 2015, 02:02:49 AM
staking will say reward, and have an amount of .617283 or .611111
Staking will say Interest, and node incentive reward will say Reward.
September 24, 2015, 05:07:03 PM
incentive will say reward, and have an amount of .617283 or .611111
doh nice catch I must have been tired when I wrote that
doh nice catch I must have been tired when I wrote that
September 24, 2015, 04:03:22 PM
What category do incentive transactions have? I've been running a node for days with an 'ok' network status and all transactions have a 'generate' type. Is it staking or incentive?
September 24, 2015, 12:44:14 PM
Ok cool, that gave me
"{"result":{"version":"Vanillacoin:0.3.6","protocolversion":60039,"walletversion":10500,"balance":0,"newmint":0,
"stake":0,"blocks":213911,"moneysupply":10625162.69303,"connections":6,"difficulty":28538.1220888124,"keypoolsize":101,"paytxfee":0.0005},"id":"123"}"
Is there any guide or command list somewhere? I've read the readme but it only explains the install and launch.
"{"result":{"version":"Vanillacoin:0.3.6","protocolversion":60039,"walletversion":10500,"balance":0,"newmint":0,
"stake":0,"blocks":213911,"moneysupply":10625162.69303,"connections":6,"difficulty":28538.1220888124,"keypoolsize":101,"paytxfee":0.0005},"id":"123"}"
Is there any guide or command list somewhere? I've read the readme but it only explains the install and launch.
http://vanillacoin.net/wiki/RPC/Commands
If a command requires parameters, like encryptwallet, it's just:
curl --data-binary '{"jsonrpc": "1.0", "id":"123", "method": "encryptwallet", "params": ["replacethispassword"] }' -H 'content-type: text/plain;' http://127.0.0.1:9195/
September 24, 2015, 12:34:21 PM
Ok cool, that gave me
"{"result":{"version":"Vanillacoin:0.3.6","protocolversion":60039,"walletversion":10500,"balance":0,"newmint":0,
"stake":0,"blocks":213911,"moneysupply":10625162.69303,"connections":6,"difficulty":28538.1220888124,"keypoolsize":101,"paytxfee":0.0005},"id":"123"}"
Is there any guide or command list somewhere? I've read the readme but it only explains the install and launch.
"{"result":{"version":"Vanillacoin:0.3.6","protocolversion":60039,"walletversion":10500,"balance":0,"newmint":0,
"stake":0,"blocks":213911,"moneysupply":10625162.69303,"connections":6,"difficulty":28538.1220888124,"keypoolsize":101,"paytxfee":0.0005},"id":"123"}"
Is there any guide or command list somewhere? I've read the readme but it only explains the install and launch.
http://vanillacoin.net/wiki/RPC/Commands
If a command requires parameters, like encryptwallet, it's just:
curl --data-binary '{"jsonrpc": "1.0", "id":"123", "method": "encryptwallet", "params": ["replacethispassword"] }' -H 'content-type: text/plain;' http://127.0.0.1:9195/
September 24, 2015, 12:30:44 PM
Ok cool, that gave me
"{"result":{"version":"Vanillacoin:0.3.6","protocolversion":60039,"walletversion":10500,"balance":0,"newmint":0,
"stake":0,"blocks":213911,"moneysupply":10625162.69303,"connections":6,"difficulty":28538.1220888124,"keypoolsize":101,"paytxfee":0.0005},"id":"123"}"
Is there any guide or command list somewhere? I've read the readme but it only explains the install and launch.
"{"result":{"version":"Vanillacoin:0.3.6","protocolversion":60039,"walletversion":10500,"balance":0,"newmint":0,
"stake":0,"blocks":213911,"moneysupply":10625162.69303,"connections":6,"difficulty":28538.1220888124,"keypoolsize":101,"paytxfee":0.0005},"id":"123"}"
Is there any guide or command list somewhere? I've read the readme but it only explains the install and launch.
September 24, 2015, 12:21:45 PM
I dont understand how to manage vanillacoin on linux. I have started vanillacoind, I then use the command "screen -x vanillacoind" but I don't know what to do from here.
How do I know when I'm synced?
How do I get a wallet address?
How do I send coins?
How do I backup wallet?
etc.
Thx in advance
How do I know when I'm synced?
How do I get a wallet address?
How do I send coins?
How do I backup wallet?
etc.
Thx in advance
You need to use rpc commands. Try this one from user while vanillacoind is running:
curl --data-binary '{"jsonrpc": "1.0", "id":"123", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:9195/
To kill vanillacoind, I use screen -x vannilacoind and then kill the process with Ctrl-c. Don't know if that's the best way.
September 24, 2015, 12:12:53 PM
I dont understand how to manage vanillacoin on linux. I have started vanillacoind, I then use the command "screen -x vanillacoind" but I don't know what to do from here.
How do I know when I'm synced?
How do I get a wallet address?
How do I send coins?
etc
Thx in advance
How do I know when I'm synced?
How do I get a wallet address?
How do I send coins?
etc
Thx in advance
September 24, 2015, 11:41:32 AM
So many good things happening with this coin right now!!
First person to get 10 btc to the exchange to buy this up is going to be a wealthy SOB.
First person to get 10 btc to the exchange to buy this up is going to be a wealthy SOB.
September 24, 2015, 10:10:05 AM
I see icebreaker is still spamming, therefore:
Vanillacoin is the ONLY coin that:
- Has random ports and encrypted connections so all your ISP sees is normal SSL traffic while monitoring your ports. No other coin does this
- Has full, staking mobile wallets that allow you to move your wallet.dat to your PC from your Android and iOS wallets. No other coin does this
- Requires only 1 confirmation on Poloniex (other than BTC, which also requires 1 confirmation)
- Only coin to have near-instant 0 confirmation transactions without master nodes. No other coin has done this
Vanillacoin is the ONLY coin that:
- Has random ports and encrypted connections so all your ISP sees is normal SSL traffic while monitoring your ports. No other coin does this
- Has full, staking mobile wallets that allow you to move your wallet.dat to your PC from your Android and iOS wallets. No other coin does this
- Requires only 1 confirmation on Poloniex (other than BTC, which also requires 1 confirmation)
- Only coin to have near-instant 0 confirmation transactions without master nodes. No other coin has done this
September 24, 2015, 10:03:13 AM
The vanilla wallet is compiled with many static libraries.
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
personally i prefer static builds for security related apps, because a lib can attack its host-app.
if its just a file somewhere on the system it may get updated unnoticed (i tend to update security apps more carefully than normal libs).
that just means someone has to rebuild if a "normal" security hole is found in a lib: not a big issue IMHO
If a hacker has access to a lib, it has access to the host program as well, so it doesn't make a difference.
Seeing how often (for example) openssl has been updated for severe security issues recently, I think building it statically in a cryptocoin wallet is to be considered a security issue.
YMMV of course.
And before people start attacking me, I'm not bashing the coin, just saying what my concerns are.
Maybe your concern has a point from your perspective but as you can see the opposite is true for many others including this coins dev. You have made your idea clear but I think you might be having trouble accepting that this is not going to change? From my point of view you are pushing system security onto the dev rather than taking it into your own hands. The simple solution, don't compile from source if you aren't comfortable with it.
I don't agree with what you are saying but in order to avoid an offtopic and starting an endless discussion, I'll just add that the issue is not only for people compiling it, but also for people using precompiled binaries.
And if people using VNL are fine with that, then it's ok ;-)
See here for reason:
https://bitcointalksearch.org/topic/users-of-bitcoin-core-on-linux-must-not-upgrade-to-the-latest-version-of-openssl-919373
edit: Also, bitcoin core is still forced to make everyone update once in a while. See April 8, 2014: https://bitcointalksearch.org/topic/bitcoin-core-bitcoin-qt-091-released-update-required-562400
September 24, 2015, 07:59:01 AM
The vanilla wallet is compiled with many static libraries.
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
personally i prefer static builds for security related apps, because a lib can attack its host-app.
if its just a file somewhere on the system it may get updated unnoticed (i tend to update security apps more carefully than normal libs).
that just means someone has to rebuild if a "normal" security hole is found in a lib: not a big issue IMHO
If a hacker has access to a lib, it has access to the host program as well, so it doesn't make a difference.
Seeing how often (for example) openssl has been updated for severe security issues recently, I think building it statically in a cryptocoin wallet is to be considered a security issue.
YMMV of course.
And before people start attacking me, I'm not bashing the coin, just saying what my concerns are.
Maybe your concern has a point from your perspective but as you can see the opposite is true for many others including this coins dev. You have made your idea clear but I think you might be having trouble accepting that this is not going to change? From my point of view you are pushing system security onto the dev rather than taking it into your own hands. The simple solution, don't compile from source if you aren't comfortable with it.
I don't agree with what you are saying but in order to avoid an offtopic and starting an endless discussion, I'll just add that the issue is not only for people compiling it, but also for people using precompiled binaries.
And if people using VNL are fine with that, then it's ok ;-)
September 24, 2015, 07:43:00 AM
The vanilla wallet is compiled with many static libraries.
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
personally i prefer static builds for security related apps, because a lib can attack its host-app.
if its just a file somewhere on the system it may get updated unnoticed (i tend to update security apps more carefully than normal libs).
that just means someone has to rebuild if a "normal" security hole is found in a lib: not a big issue IMHO
If a hacker has access to a lib, it has access to the host program as well, so it doesn't make a difference.
Seeing how often (for example) openssl has been updated for severe security issues recently, I think building it statically in a cryptocoin wallet is to be considered a security issue.
YMMV of course.
And before people start attacking me, I'm not bashing the coin, just saying what my concerns are.
Maybe your concern has a point from your perspective but as you can see the opposite is true for many others including this coins dev. You have made your idea clear but I think you might be having trouble accepting that this is not going to change? From my point of view you are pushing system security onto the dev rather than taking it into your own hands. The simple solution, don't compile from source if you aren't comfortable with it.
September 24, 2015, 07:22:56 AM
The vanilla wallet is compiled with many static libraries.
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
personally i prefer static builds for security related apps, because a lib can attack its host-app.
if its just a file somewhere on the system it may get updated unnoticed (i tend to update security apps more carefully than normal libs).
that just means someone has to rebuild if a "normal" security hole is found in a lib: not a big issue IMHO
If a hacker has access to a lib, it has access to the host program as well, so it doesn't make a difference.
Seeing how often (for example) openssl has been updated for severe security issues recently, I think building it statically in a cryptocoin wallet is to be considered a security issue.
YMMV of course.
And before people start attacking me, I'm not bashing the coin, just saying what my concerns are.
September 24, 2015, 07:15:37 AM
The vanilla wallet is compiled with many static libraries.
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
personally i prefer static builds for security related apps, because a lib can attack its host-app.
if its just a file somewhere on the system it may get updated unnoticed (i tend to update security apps more carefully than normal libs).
that just means someone has to rebuild if a "normal" security hole is found in a lib: not a big issue IMHO
September 24, 2015, 07:09:53 AM
WOW, gjhiggins the famous scammer behind several C-CEX ico scams also saying that VNL is a scam.
This is very worrying.
This is very worrying.
September 24, 2015, 06:25:04 AM
The vanilla wallet is compiled with many static libraries.
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
Other than a build annoyance for people wanting to compile themselves, it is a security issue.
When your operating system does security updates on those libraries, the wallet will be unaffected by those updates and will keep being vulnerable.
This is pretty common for windows applications, much less on unix.
See here for the discussion:
https://bitcointalksearch.org/topic/m.12499004
I warned you ;-)
September 24, 2015, 06:05:20 AM
IMO Monero guys are so pissed, because we took them a lot of potential investors (look at monero chart).
My advice for MONERO community sell part of your coins and buy Vanilla, after you earn a lot of money on VNL you can rebuy XMR at lower price.
My advice for MONERO community sell part of your coins and buy Vanilla, after you earn a lot of money on VNL you can rebuy XMR at lower price.
September 24, 2015, 05:12:56 AM
John answer is excellent 
Jump to: