Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Feedback

  • BF$

    0 [ Donate ]

Everything posted by KawaiiCrypto

  1. Monday March 19, 2018 00:38:44 (am) in time zone Europe/London (GMT) Address: DJSh7TfKnMdhGojPpghPrN5f1m5udhqWiU Good luck everybody.
  2. Yup. No reason to allow anyone have access to the wallet, in case they guess/bruteforce the username/password.
  3. Good tutorial, worked perfectly.. One note though, you should always have rpcallowip= in your denarius.conf unless you have a really good reason not to have it there. This limits which IPs can connect to your wallet to run commands on it. In my example, only localhost (the computer the wallet is running on) can send commands.
  4. Good tutorial, will try it in a couple of days.. One note though, you should always have rpcallowip= in your denarius.conf unless you have a really good reason not to have it there. This limits which IPs can connect to your wallet to run commands on it. In my example, only localhost (the computer the wallet is running on) can send commands.
  5. Very cool idea! I will wait until block after block 619k to make my guess though.
  6. A few people asked about a more interactive chart about the potential masternode earnings.. Ask and you shall receive. http://denarius.win/ If you want to see the dollar amounts in BTC, hover your mouse over the dollar value. Page is updated every 5 minutes.
  7. In the next release of the wallet, the fix to the low PoS rewards will be included, making them 6% interest/year.
  8. Nice guide, I only read through it very fast, did not try it out (yet).. A couple of notes though. There is no need to install libminiupnpc-dev and libqrencode-dev, since libqrencode is for the QT wallet and UPNP is only needed if your wallet software is behind a NAT device. However, building without libminiupnpc requires you to pass the USE_UPNP flag when you run make, like so: make -f makefile.unix USE_UPNP=- Regarding libdb++-dev - as far as I know, the version shipped with ubuntu (and debian I think) will break backwards compability with old wallets. This does not have to be an issue, but it could be if you in the future find an old wallet.dat created by an older version of the Denarius wallet. To fix this, install libdb4.8++-dev like so: sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get -y install libdb4.8++-dev
  9. An even more updated chart. Masternode collateral has been agreed to be 5k, so will of course only include this number from now on.
  10. I have updated the chart to reflect the current denarius price and circulating supply. I originally suggested 2k-3k coins for masternode collateral.. I still think 3k would be a good number, but for fun I have included 3333 as it goes great with the general tribus (three) theme of Denarius I think. Having a slightly lower collateral requirement would probably result in more nodes spread out, which would be beneficial to the network.
  11. Nope, I never said that because masternodes is a buzzword Denarius should have them. I said that because masternodes is a buzzword, if Denarius gets them, it would bring added attention to the project. Yes that is generally how markets work, early adopters gets a bigger return because they took on more risk. The people who bought the ethereum ICO earned a boatload of money, because they assumed the risk and decided it was worth it. People who bought in later earned less. Now.. Will a masternode release help increase price? Yes I would think so. Will price drop some after the initial knee-jerk fomo rally? Yes, I would think so, like every other rally someone will buy the top, no matter what announcement is made. Will masternodes hurt the project? No, I do not think so. You have not answered my question: Do you think masternodes would hurt Denarius?
  12. Hmm I would think it is possible to compile with 2GB of RAM. There is only one way to find out - try.
  13. If the only thing a coin has going for it is masternodes, then it makes no sense. , but denarius has other things, like encrypted messaging, stealth transactions and low block time.. Also, even though it is a PoS-only coin after a couple of years, supply will not inflate wildly. Yes it does give early adopters a nice payoff.. But that can be said for everything good added to the coin or the ecosystem around the coin. Masternodes accomplishes a few things: It reduces available coin supply (yes this is only a benefit to people already hodling the coin or buys before MNs is released). It encourages people to run stable nodes by giving them a financial incentive to do so, thus making the coin more decentralized (unless everybody hosts in the same datacenter). Because of masternodes being a buzzword in crypto circles, it would bring added awareness to the Denarius project. I too think that Denarius can be big without masternodes, but I fail to see how masternodes would be a bad thing - at worst, things will stay as they are, with an additional feature added to the wallet. Who is the community is a good question indeed. Of course I do not assume that everybody in the DNR community is in the discord and I agree that maybe the rumors of masternodes could have been communicated better. However as far as I know, Carsen has not stated that masternodes WILL be a part of the denarius wallet, he simply stated that it was something he is spending some time on, to see if it can be done. I see the problem that websocket-based chat apps/sites are blocked in coporate networks, so it might be hard to keep up with everything happening. However, on this very site there has been a thread with a poll since July 13th regarding masternodes. It has been annouced in the bitcointalk thread as far as I know and 3/4th of the votes wanted masternodes, so everybody who checked the thread knew that it was a possibility back then, just as it is a possibility now, not a certainty. To be honest I do not see how mining is different from buying a coin. Sure, you do not need the technical skills, but so what? If I mine the coin or if I buy the coin, I can dump it all the same. Actually I personally would probably dump some of it sooner if mining because I have to pay for electricity.. Maybe you are right, maybe masternodes does nothing to benefit Denarius in the long run.. But my question is this: Do you think masternodes would hurt Denarius? Even though we have opposing views, I do really appreciate your input. It is dangerous for a coins community to be inside an echo chamber where everybody hypes each other up.
  14. Actually on January 14th, Denarius will be 7 months old. ;-)
  15. Basically, yes. You configure each node to listen on a different IP and port..
  16. Each masternode needs a unique, public IP address, but many VPS providers allows for configuration of multiple IPs to a single VPS, for a fee.
  17. Here is a small graphic that might help you guys decide on which numbers you like. This chart is correct (I hope xD), assuming that every block is a PoW block and that block reward is 3 (it will change to 4 soonish) and that masternodes gets 1/3rd of block reward and that price stays at $0.8 which it most likely will not AND that Carsen does not run any masternodes or put any of his premine into circulation. Let me know if you find any flaws in this and I will correct them. Yes, I realize that the last line says that 101.33% of supply will be locked in masternondes but I included it because we are pretty close to 1,650,000 circulating supply.
  18. Well, PoSv3 will make it a whole lot easier to estimate how much the denarius supply will be x months into the future which could become useful. It will also make it a lot easier to calculate the actual PoS reward since it would become a function depending on only the current money supply and the interest, which is set in stone. On the other hand, and please correct me if I am wrong, but regular PoS would keep the inflation a bit lower because the reward would depend on the amount of coins staked instead of depending on the entire coin supply. So as some coins are always kept on exchanges,, less coins would stake resulting in lower overall PoS rewards added to the money supply. Currently https://chainz.cryptoid.info/dnr/ reports 76 peers seen in the last 24 hours, which is not that many. If @Carsen implements PoSv3 and then sets it to activate 1-2 months into the future, I see no reason why nodes should not have been updated by then - at the very least, pools, block explorers and exchanges wallets would have been updated and people who have not seen that a new wallet has been released will notice when their PoS blocks all starts to orphan, then go to the thread and then see that a new version is out. And as @buzzkillb said, if we are going to hardfork, it might be worth really considering what other changes needs a hardfork and incorporate them as well, preferably with an activation around the same time as PoSv3. Changes that spring to mind are the DNS functionality and masternodes, which 76% of voters said they want. Of course if either of these two things were to be incorporated, the activation date would likely be pushed further into the future.
  19. Here are my thoughts on these points. Whales are almost present on every coin, it matters not if the coin implements masternodes or not, the whale could in theory decide to dump their entire stash, but why would they? Partial dumping maybe, but dumping the entire stash is very unlike in my opinion. This is true of hosting regular nodes as well to some degree. Again, true for both masternodes and regular nodes. True some might be faced with this dilemma. But if there are for instance 200 nodes, chances are that not everyone will liquidate their nodes collateral at once. I have no experience in the legal part of crypto, but will say this; Chances are that even if one country decides to ban masternode tech, other countries will allow it, so it is simply a matter of moving the masternode hosting to one of those countries. Same as above. Not sure this is has to be a bad thing. Descicions regarding masternodes are like walking on a knifes edge. Too much collateral required means not much decentralization, too little collateral and masternodes will probably pop up on less than able hardware making DoS attacks easy. Also, the more DNR collateral is required to run a masternode, the less DNR is on the market meaning less selling pressure. Too high a reward and miners will complain about losing too much revenue but will incentivize masternode operators to keep running their masternode. Too small a reward and masternode operators might decide that running their node is not profitable enough, thus making them shut down their node and sell off their collateral. I have previously suggested making the collateral 2000-3000 DNR. This is just off the top of my head, but let me know what you guys thoughts are.
  20. I bought a Raspberry Pi 3 a while ago and got it recently. So of course I decided to run my denarius wallet on it, so it can stake always without my computer being on. The operating system is Raspbian Stretch, so I assume this tutorial will work for debian stretch as well. Start by opening a terminal and paste the following code to install dependecies: sudo apt-get update sudo apt-get upgrade -y sudo apt-get install autoconf libtool libssl1.0-dev libboost-all-dev libminiupnpc-dev -y Because compiling can take up a large amount of RAM and the raspberry Pi only has 1 gigabyte of it, let us create a swapfile: cd / fallocate -l 4G swapfile chmod 0600 swapfile mkswap swapfile swapon swapfile Now, because the daemon requires Berkeley database version 4.8 to work, we need to download, compile and install it since that is not included in the software repositories. cd ~/Downloads wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz tar -xzvf db-4.8.30.NC.tar.gz cd db-4.8.30.NC/build_unix/ ../dist/configure --enable-cxx make sudo make install Now, let us download the denarius source code and compile it. cd ~/Downloads git clone https://github.com/carsenk/denarius.git cd denarius/src Because we use a custom Berkeley library, we need to specify its location in the makefile, so go ahead and open that up using nano: nano makefile.unix look for this line: DEFS += $(addprefix -I,$(CURDIR) $(CURDIR)/obj $(CURDIR)/json $(BOOST_INCLUDE_PATH) $(BDB_INCLUDE_PATH) $(OPENSSL_INCLUDE_PATH)) Change it to this line: DEFS += $(addprefix -I,$(CURDIR) $(CURDIR)/obj $(CURDIR)/json $(BOOST_INCLUDE_PATH) $(BDB_INCLUDE_PATH) $(OPENSSL_INCLUDE_PATH) /usr/local/BerkeleyDB.4.8/include/) Press CTRL+O to save the file, press enter to verify the filename, then press CTRL+X to exit nano. Now we are ready to compile it! When you have typed in this command, prepare to wait for a while, maybe grab a good book or go to the denarius gitter chat to socialize. Compiling took 63 minutes on my Pi, it will depend on your swapfiles read/write performance and if you have overclocked your Pi. make -f makefile.unix -j4 LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib" Now since we are using a custom library, we need to tell the operating system to let programs use that. To do that, we need to edit the file /etc/ld.so.preload: nano /etc/ld.so.preload Add the following line to the file, then save and exit, like before: /usr/local/BerkeleyDB.4.8/lib/libdb_cxx-4.8.so and reboot: sudo reboot Now, your denariusd is ready to run and you set it up like you always would.
  21. Since the wallet already has price data, it would be cool if there was an RPC call to get current price data in both BTC and USD.
  22. Here is my very not production ready chart, along with the data I used to make it. Note that I gave DASH an advantage, since they are switching to 2MB blocks in September. Also note that I assume that each transaction only includes one input and one output, which is a naive approach, since that requires that the fee + amount sent to the receiving address is the same as the value of the input, which is rarely will be. But still, having the same tx size for all coins makes comparison easier. ALSO note, that I have no idea of how to look up the excact blocksize of coins based off new style bitcoin source code, which is why BTC, BCH and DASH have blocksizes which are probably some bytes away from the correct number.. And here is the chart (feel free to laugh xD)
  • Create New...