Jump to content


Popular Content

Showing content with the highest reputation since 09/17/2017 in all areas

  1. 4 points
    I've extracted the code to verify signed messages and make a standalone library https://github.com/chelahmy/dnrverify/ My intention is to implement a signed message verification function in PHP. I've tried https://github.com/BitcoinPHP/BitcoinECDSA.php and https://github.com/scintill/php-bitcoin-signature-routines but both failed to verify Denarius signed messages. They used the technique from this link https://crypto.stackexchange.com/a/18106 which seems to be different from the one used in Denarius. I noticed modular arithmetic is applied in Denarius code. So, I just extract the signed-message verification code from Denarius and see if I can make a PHP version. Digital signature has wide applications which should be initiated by the cryptocurrency world. Every digital wallet has private keys which are ready to be used to digitally sign anything, other than just to sign spending transactions. The other side of the applications just need to verify the signed something without necessarily going through wallets.
  2. 2 points
    Yup everything looks good there! Your wallet is setup for staking, note the enabled: true certifies staking is enabled for your wallet, staking: false, just means it is not currently staking as your weight is also 0. You need to have coins that have matured for a minimum of 8 hours. It can take some time to find a PoS block due to PoW making generally 70% of blocks right now.
  3. 2 points
    Hello everyone! I thought I would start a topic here in Development for the upcoming Denariium client. It is still a work in progress and I will try to update this thread as updates come. Currently I have the denariiumx-server syncing with denariusd perfectly, I just need those who wish to setup volunteer Denariium nodes for connection with the Denariium client. It is currently in the works, the github repos are available here: https://github.com/carsenk/denariiumx-server (The Denariium Server) (Python 3.6 required) https://github.com/carsenk/denariium (The Denariium Client) (Python 2 required) If you have a fix or additions, etc. please put a pull request up on the github! I have yet to test if the Denarius WIF, P2PKH, P2SH, P2WPKH, etc. are correct yet. I recently updated the way denariusd returns the getblock RPC command, this change was needed for the Denariium code to sync blocks properly. I may eventually be adding the estimatefee RPC command as well to add this functionality to Denariium (currently it is running off a fakeestimationfeedaemon). Once everything is setup and running smoothly the website denariium.org will come with more information, along with downloads to the client.
  4. 1 point
    I'm Tim, from the New England area in the US. Just started into the mining business after a few nights of talking about various investment ideas with my dad. We each have a machine at our house and are runnning a gtx 1060 6gb. Still learning a lot every day but it's a fun project that I hope to be able pay off debt and make some extra money with when Denarius takes off through the roof in the future.
  5. 1 point
    So I decided to fork the PHP repo https://github.com/chelahmy/BitcoinECDSA.php Enjoy!!!!
  6. 1 point
    Actually Denarius only made a simple change in the original Bitcoin code by replacing const string strMessageMagic = "Bitcoin Signed Message:\n"; with const string strMessageMagic = "Denarius Signed Message:\n"; In fact, the verification process ignores address prefix. Thus, any Bitcoin or Bitcoin-based Altcoin can also use the same code to verify its signed messages by just setting the proper strMessageMagic. Anyway, I'll maintain my GitHub repo as dnrverify and keep highlighting Denarius. Another thing, both the PHP repos above can actually verify Denarius signed messages. However, they hard-coded the strMessageMagic, and just replacing it with "Denarius" simply doesn't work because of the following original Bitcoin code CDataStream ss(SER_GETHASH, 0); ss << strMessageMagic; ss << strMessage; where each time a string is appended to the ss the internal data structure keeps it as string length + string. Thus, the final data will be strMessageMagic length + strMessageMagic + strMessage length + strMessage. Both the PHP repos above implement something like the following $messageHash = hash('sha256', hash('sha256', "\x18Bitcoin Signed Message:\n" . numToVarIntString(strlen($message)).$message, true), true); The "\x18" is actually the length of "Bitcoin Signed Message:\n" which can be calculated with the following function numToVarIntString(strlen("Bitcoin Signed Message:\n")) "Denarius Signed Message:\n" is just one byte longer and can be pasted as "\x19Denarius Signed Message:\n". Hence, the technique of that link https://crypto.stackexchange.com/a/18106 is valid for Denarius and Bitcoin-based Altcoins. However, the modular arithmetic technique in Bitcoin code is more efficient. I'm going to patch one of the PHP repo.
  7. 1 point
    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.
  8. 1 point
  9. 1 point
    It worked, finally started getting some staking returns. Moving my wallet to my dedicated mining server. Still awaiting for it to sync to network.
  10. 1 point
    Hi! Please help me with the following issue/ Denarius wallet generates an error: this had happened after power loss, I've tried to repear but it doesnt help.
  11. 1 point
    Denarius v1.0.7.0 10/8/2017 - v1.0.7.0 - Miscellaneous Fixes -Added new bootstrap.dat (Block 277757, 10/6/2017, Compressed .zip) c60c1bc - Updated getblock RPC Command, Inline with newer Bitcoin Core Releases. c85ae7a - v1.0.7.0 Increment and Checkpoints 7503976 - Removed Staking Estimation Reward Temporarily 4662285 - Fixed Display of Market Values 61a0e84 - Fixed Overview Page USD Balance Display a35d228 - Renamings for Deb Building 3e55d40 - More Staking Estimation Tab changes & Checkpoints da22e61 - Updated Overview Page GUI 8a91064 - Updated TX Icons 3e666fe - More icons and GUI Fix f15fe5b - More GUI Fixes 1380458 - Updated Makefiles Side note: A new branch labelled "DNS" was created which will be for potentially a future v1.5, this branch will include code for Namecoin names functionality and a DNS Server that will interface with it. It is still in its very early stages and needs feedback from developers and fixes. It is not recommended to run this branch on any production servers or important wallets. Windows and macOS Binaries are available below, along with the blockchain bootstrap up until block 277757. Windows Installer for Denarius-QT: https://github.com/carsenk/denarius/releases/download/v1.0.7.0/DenariusInstaller.exe (MD5 Checksum: C258FE2654E68658D7093E46C9BB0505) Windows-QT Wallet Download:https://github.com/carsenk/denarius/releases/download/v1.0.7.0/Denarius-QT.zip (MD5 Checksum: 205B3D1209D14B263FBE8E9F67B9CEA0) macOS-QT Wallet Download: https://github.com/carsenk/denarius/releases/download/v1.0.7.0/Denarius-v1070.dmg (MD5 Checksum: 552F5249285DE3914B6CE4613FC62576) DNR Blockchain Bootstrap (Block 277757, Compressed .zip, Unzip and put bootstrap.dat in your AppData/Roaming/Denarius or ./denarius folder to import): https://github.com/carsenk/denarius/releases/download/v1.0.7.0/bootstrap277757-10-6-2017.zip You can view this release on the Github at: https://github.com/carsenk/denarius/releases/tag/v1.0.7.0 Don't forget to join our Gitter or Slack chats if you haven't already! https://gitter.im/denariusproject/Lobby https://join.slack.com/t/denarius/shared_invite/enQtMjAzOTk1OTA5NzE3LTMwZDc0YTY3NDI5ZmRmYzNiZThlMzYxYzMwYTBlYmRkOWI3YWExMjAxMzdkYTE3OTI0ZjY5NWYzY2RkZjQzOWQ
  12. 1 point
  13. 1 point
    @jtmining17 The RPC User and Password values can be set to anything. The main setting here you want is the staking=1. Everything looks fine in your conf to me, so the next thing I would check is by going to in the wallet "Help->Debug Window->Console" and then type in "getstakinginfo" please paste what is found here if your wallet is encrypted you need to ensure it is unlocked for staking via the GUI as well.
  14. 1 point
    Do I just compile and run it in order to run a node?
  15. 1 point
    I don't think a coin with active development, threads and community can be called dead Our volume is a bit down lately, but we're light years away from being "dead".
  16. 1 point
    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 / dd if=/dev/zero of=swapfile bs=1M count=4000 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.
  17. 1 point
    Sounds like it is potentially a permissions issue with your X server on your OS install. You can try the below to set the permissions to the root user. You need to allow the root user access to the X server: xhost local:root And point the command to the right DISPLAY: sudo DISPLAY=$DISPLAY gedit /etc/profile
  18. 1 point
    This is what it says after running ./Denarius "Denarius: cannot connect to X server" No errors in the compile. Will try kawaii's guide next and see if that changes anyhting.
  19. 1 point
    Correct, MATE 16.04. Anyone else try this out?
  20. 1 point
    Just post in here good songs that help you feel relaxed or help you focus on your work here.
  21. 1 point
    Awesome tutorial @KawaiiCrypto ...If you want to run the full Denarius QT Wallet on a Raspberry Pi 3, then do the following: Install the deps, you may only need to install libqt4-dev and libqrencode-dev packages if you followed the tutorial above. sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev libboost-all-dev libminiupnpc-dev libqt4-dev libprotobuf-dev protobuf-compiler libqrencode-dev -y Then install the final dependency needed for Denarius QT, this is an alternative method to Kawaii's above that does not require you to compile the Berkeley DB 4.8 sudo apt-get install software-properties-common sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev Create the swapfile on your Pi (same as Kawaii's above) so that you can compile the code, since it has only 1GB of RAM. This creates a 4GB Swapfile. cd / dd if=/dev/zero of=swapfile bs=1M count=4000 chmod 0600 swapfile mkswap swapfile swapon swapfile Then we just need to clone our Denarius repository: cd ~/Downloads git clone https://github.com/carsenk/denarius.git cd denarius Once inside our denarius directory, we need to tell Qt (qmake) to setup our makefile for compiling: qmake "USE_LEVELDB=1" "USE_UPNP=1" "USE_QRCODE=1" denarius-qt.pro USE_LEVELDB=1 is required, USE_UPNP and USE_QRCODE are optional. Now we are finally ready to make! make -j4 (4 is the number of cores of your processor that you want to use for compiling, generally on the Pi3s you can use 4 cores) Once it is done building and if you didn't get any errors you will be able to run the following to launch the Denarius QT Wallet! ./Denarius If you run into any issues during the first time trying to make the QT, try going into the /src directory from Kawaii's tutorial above and compiling the denariusd first and then compile the QT. (Also when compiling denariusd in Kawaii's tutorial, you can avoid having to edit any makefiles by installing the Berkeley DB 4.8 from the PPA I listed above).
  22. 1 point
    Sweet work @KawaiiCrypto , my weekend project!
  23. 1 point
    updated to show ccminer is now yiimp.eu
  24. 1 point
    Added the macOS v1.0.6.0 wallet finally! https://github.com/carsenk/denarius/releases/download/v1.0.6.0/Denarius-v1060.dmg (MD5 Checksum: 85DC74D1BBDAEC109D539C039D2546ED)
  25. 1 point
    Hey guys! Time to show off your Mining Rigs Ill go first lol: RIG SPECS: (1)CPU : Intel® Celeron® Processor G4400 (2)Motherboard : MSI Z170A GAMING PRO CARBON (3)GPU : MSI GAMING X RX 470 8GB * 7 (4)Memory : Kingston 8GB DDR4 2400 (5)SSD: 120GB (6)PSU : EVGA 1300 G2 (7)Other : USB 3.0 PCI-E Express 1x To 16x Extender Riser Card Adapter * 7 (8)System : Windows 10 N Build Cost: £1800 (made that back in 7 weeks of mining Zcash) Output: Hashing Power: 2100 Sol/s or 210 MH/s Temps: 50-60 Degrees Power Uages: Around 1100 Watts DNR Mining: Currently 36 DNR a day Power Cost: £80 per Month PICS: Building at my Bro's House: Finished building / all working. Now its perm home in my computer room mining away: I also have pics of the each stage of our build if anyone is interested. Just a lot of pics to post haha.
  26. 1 point
    My first mini rig and first pc build for gaming 3 gtx 1070 1 gtx 1060
  27. 1 point
    I'm pretty sure I got all of you beat: And no there isn't more, that's all of it.
  28. 1 point
    CPU - AMD Ryzen 7 1700X w/ liquid cooling RAM - 32 GB DDR4 3200+ GPU - 6 GTX 1080s (MSI Gaming X and EVGA FTW2) PSU - 1000w EVGA and 850w EVGA ~300MH/s mining DNR per rig, of which I currently only have 2
  29. 1 point
    JailCoin - the more jailtime you have, the more coins you get.
  30. 1 point
    Gday from Australia fellas ! Current setup Asus Z270-p Prime LGA 1151 Mb i3-7100 3.9ghz cpu 8gb RAM AMD R9 295x2 x3 water cooled will be x4 soon if i can find one im using AMD driver 16.3.2, seems to be the most stable. ebay risers Corsair HX1200i and 900w PSU's Mining frame is 25mm aluminium tube and plastic connectors from local hardware (Bunnings) the base and backing for SSD's and PSU's and MB is alucobond cladding used on commercial buildings mostly, got that from off cuts pile at a site i was working at. I am a carpenter so if anyone needs mining frames, send me a PM. happy mining !
  31. 1 point
    Well you got me beat RecoStar, thats a nice setup! Mine is: 4 x R9 380s 1300w EVGA Supernova PSU 4GB RAM 128GB SSD ASRock H81 Pro BTC LGA 1150 Motherboard FLOW MintCell Mining Rig Chasis with two neon green fans