Monday.
I kinda doubt it. DRK is over the shitcoiners' heads. No matter what happens with the development, they just have that mouth-open blank stare... Yeah, open source isn't going to change the price much by itself, nor are we going to see a new rash of clones, because you can't clone a thousand VPS's. My post about forgetting shitty crypto blogs was serious, preaching to anyone inside the crypto scene is an utter waste of effort - we need to get the word out to the spooks, the political dissidents, the junkies, the tax evaders, cheating spouses, etc. People sick of being cheated, violated, and robbed at gunpoint by politicians are not bad people. Did I say that? I'm one of them, but the blunt truth is that the sentient have been out-competed by the clinical sociopaths. We need to develop better predation tactics to survive.Do we? Is the only way to counteract sociopaths to become even more ruthless than them? I think people should just stop being so gullible and finally accept that there are wolves in sheeps clothing among us. If everybody recognized the wolves there would be no problem. Wolves like easy prey. Sociopaths like easy prey, they always isolate the sickest, weakest sheep. They hate resistance. The problem lies in all the sheeple who believe that the "charming wolf" (politicians and other cultleaders) is their friend, ... until the end.  |
|
|
|
Nobody promised you anything. You are stuck in this impatient daytrader mentality that desires to get rich quick, all the time. There is no deciding moment. I doesn't work this way. The really successful coins always need years to grow and develop. Get used to it, darkcoin is here to stay.  |
|
|
|
My name says it all!!!
It does.  |
|
|
|
Monday.
I kinda doubt it. DRK is over the shitcoiners' heads. No matter what happens with the development, they just have that mouth-open blank stare... Yeah, open source isn't going to change the price much by itself, nor are we going to see a new rash of clones, because you can't clone a thousand VPS's. My post about forgetting shitty crypto blogs was serious, preaching to anyone inside the crypto scene is an utter waste of effort - we need to get the word out to the spooks, the political dissidents, the junkies, the tax evaders, cheating spouses, etc. Yeah, we should create advertizements with slogans like what you just said in combination with darkcoin logo etc, and share them on libertarian an anarchist sites/forums. I know a few. :-) First get all of them on board, and then we widen the base from there. I like your 3% rule.  Or should I say 3% promise. PS: looking forward to todays xpool payment... need my daily dose... |
|
|
|
That's where the problem is. Google Translate is the reason for many unwanted pregnancies  I yawn from the boredom of begging trolls :-P
LMAO.   |
|
|
|
Well, I would not advise that unless you are fluent in Turkish lol, I was just using google translate. |
|
|
|
yawn
Neden esneme mi?* I declare darkish* the new official language of darkcoin. ... just kidding, just kidding. *turkish |
|
|
|
Hey I am on Central time, GMT-5. I meant to send that earlier I am on my way home now will send it a little later.
No problem, thanks in advance. I am GMT+2, I just woke up. Sent. Check your messages. Thanks, already extracting graphics from the photoshops. |
|
|
|
Hey I am on Central time, GMT-5. I meant to send that earlier I am on my way home now will send it a little later.
No problem, thanks in advance. I am GMT+2, I just woke up. |
|
|
|
I created all the GUI graphics with a graphic designer that works with me in real life, I still have all we did. We didnt get to the coding part because when we finally chose the design and were ready to split it up into elements DRKLord went missing. Nevertheless, we still have all that good work we did and the project is alive, when the official dev team has some time to dedicate to it, it will be retaken. If we do get a new QT developer before that, then even better.
Any chance creating an official GUI that is not just for the new wallet? I would not be in need of graphics like those curvy arrows in the background, etc... they are specifically part of the Darkcoin Foundation CD, I am talking more about plain elements like buttons, checkboxes, textfields, dropdown menues, arrows, different background regions, scrollbars, etc... also a colorpalette and fonts. I want my apps to look darkcoiny, but not be mistaken with the official darkcoin stuff. I will PM you all the artwork we have so far tomorrow when I am in the office and you take it from there, this is an open source project we need everybody's input. Please don't forget this Minotaur26, I need this! Thanks. What timezone are you in? |
|
|
|
Thanks, I'm happy with my share of the booty. Mining titcoin for some booty. Makes sense! |
|
|
|
A question, how many dummy masternodes are active on the TESTNET on average and at the moment?
How can I find out?
Are only enough of them online when we are making RC bug hunting, or do people generally keep a few of them testnet masternodes active?
or is it possible to run masternode and testnet masternode side by side on the same server?
Just put testnet=1 in your conf or commandline call and run masternode count / masternode list. There are usually some up even between active testing phases. It's not too hard to run main and test net MN's alongside each other as they use different ports (9999 main and 19999 test), you don't need to get creative with IP tables, just use different datadir's (or different users) for each. Thanks, I'll try to do that. |
|
|
|
|
A question, how many dummy masternodes are active on the TESTNET on average and at the moment?
How can I find out?
Are only enough of them online when we are making RC bug hunting, or do people generally keep a few of them testnet masternodes active?
or is it possible to run masternode and testnet masternode side by side on the same server?
|
|
|
|
What I did was to check for an existing .conf file, and if it didn't exist, or if it threw an error anyway as it didn't include an rpc user/pwd, run the daemon, take the suggested name/pwd and... stick it in the .conf file, because you're going to need it next time you start the daemon before you can do anything. That's actually a great idea. The frontend could create the conf file, and save whatever you want in it. We could make the conf file editable from within the frontend itself. Save the conf file, stop the daemon, restart the daemon, all without the need to restart the frontend itself. Adding additional Nodes (addnode, as if darkcoin needs those with this fantastic masternode network) would be easy as never before. |
|
|
|
You can do that, but you'll need to generate a unique pwd for each user - otherwise you'll have a bunch of users with the same rpc credentials which is probably not a great idea. What I did was to check for an existing .conf file, and if it didn't exist, or if it threw an error anyway as it didn't include an RPC user/pwd, run the daemon, take the suggested name/pwd and... stick it in the .conf file. Ofcourse, didn't the daemon create the unique password for you in the first place? This is all rather obvious. My frontend.exe decides the rpc password randomly. On the fly, even for every start of the daemon a new rpc password, why not. It's just an rpc password, not your walletpassphrase. I was just making an example with your rpc credentials. And you assumed it will be the same for all users? I am not sure yet, but I think there is even a parameter with which you can tell darkcoind to NOT use RPC at all. I assume the reason why it keeps bitching about the missing rpc password/username is because rpc has not been deactived. Basically I look at it like when I enter mining credentials into cgminer and tell it password=x. Useless but still necessary. It's not like the password has any meaning in this case, but the pool will bitch if you don't add the password parameter. It will be a similar thing with the frontend and RPC, because who needs a password if the frontend.exe is located right next to the darkcoind.exe on the same machine controlled by the same user, and they are directly talking to each other. Therefor if it still needs those parameters I will just do: >E:\darkcoin/darkcoind -rpcuser=x -rpcpassword=y -testnet=1 rpc username and password is mainly for when you allow outside access to your server. |
|
|
|
Try it.  You're going to be seeing this: Error: To use darkcoind, you must set a rpcpassword in the configuration file:
/home/stu/.darkcoin/darkcoin.conf
It is recommended you use the following random password:
rpcuser=darkcoinrpc
rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "DarkCoin Alert" admin@foo.com
Nope , you simply add >E:\darkcoin/darkcoind -rpcuser=darkcoinrpc -rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L -testnet=1 Ofcourse, any conf file in the blockchain folder must not exist in this case, or else the daemon will still go looking for it after it starts. (and possibly override your parameters. I am not sure, have not tested this case, I keep no conf file) As I said, you can completely ommit the conf file IF you have direct shell access possibility to the daemon. (which is key) I just tested it again, and it works. The thing to understand here, is that this command is not written somewhere... it's a shell command call that the frontend.exe is making on the fly, it does not need a textfile somewhere, hence no need for a conf file. So the frontend would make commands like this for every possible thing a darkcoin wallet is supposed to do, and recieve results back from the daemon, and use the beautiful darkcoin GUI to make it look sexy. |
|
|
|
Not at all. I am not talking about RPC calls that need a specific port to be open or something.
I am talking about direct commandline communication between Frontend and darkcoind.
Frontend.exe and darkcoind.exe would best be in the same folder.
It's like when you type commandline commands by hand, but now the frontend.exe makes this for you (with the darkcoind running in the background invisible)
You still need to generate an RPC user/pwd and stick it in the conf file for that to work. At least I had to. It has nothing to do with RPC. It's not remote at all. It's direct access to the daemon on a commandline level (shell), passing it any commands and parameters you need to, and reading the return data the darkcoind itself gives back. (not going thru some port, but outputting to the shell so to speak) An example: Suppose this is the folder where the darkcoind resides: Now I simply start it by making a Commandcall and the daemon starts. I can even start it with parameters, for example: >E:\darkcoin/darkcoind -datadir=E:\blockchains/drk/ this tells the darkcoind where to look for the blockchain and wallet.dat. WITHOUT the need for any conf file telling it to do that. Everything you put in a conf file can also be added as a parameter when you start the darkcoin daemon. A conf file is not needed if you work like that. So... after the darkcoind is ready, I can make calls to it, for example getblockcount, and it will return the JSON string. >E:\darkcoin/darkcoind -datadir=E:\blockchains/drk/ getblockcount etc. I can start the darkcoind in testnet mode by making the call like that: >E:\darkcoin/darkcoind -testnet=1 I can combine any parameters: >E:\darkcoin/darkcoind -datadir=E:\blockchains/drk/ -testnet=1 and so forth. By using Adobe Air's native extensions functionality I can use ANY external executables I like and trigger their functions and pass the results/data back to the frontend. This would also work with multiple coins at the same time.  |
|
|
|
Should I give it a try?
The awesome thing about that would be that I don't need to touch/change the darkcoind at all. It would do all darkcoin related things as it already does so well.
So we don't have to debug two versions of the darkcoin software, just the darkcoind and the frontend separately.
I'm not sure. That would require adding more lines into the config files adding confusion to end users. Not at all. I am not talking about RPC calls that need a specific port to be open or an IP allowed in the conf file. I am talking about direct commandline communication between Frontend and darkcoind. Frontend.exe and darkcoind.exe would best be in the same folder. It's like when you type commandline commands by hand, but now the frontend.exe makes this for you (with the darkcoind running in the background invisible) |
|
|
|
|
Show Posts
