A complete beginners guide to installing a Bitcoin Full

Whonix lead developer wants to maintain a debian repository for the Monero GUI for two years. Comment on the proposal!

Whonix lead developer wants to maintain a debian repository for the Monero GUI for two years. Comment on the proposal! submitted by Rehrar to Monero [link] [comments]

Same lies about Dash still floating around - Time for another crackdown

This article was caught by our spamfilter because it's hosted on a reward-for-article platform (similar to steemit). Nonetheless I will respond to it, as it recycles the same old lies about Dash many of us have grown used to and it serves as in illustration that these lies and accusations are still after 6 years regurgitated 1:1 by ignorant bystanders without a single critical thought behind them.
The article is a real mess as you will notice. The author didn't even bother to edit the question section into Dash from ZCash. Anyway, that's not the real issue. This is about the section "Dash Launch And Issuance" which I am about to respond to.
The Dash cryptocurrency has a rather controversial launch and issuance as it involved a 2-day ‘instamine’ or ‘premine’
There is a huge difference between a premine and a fastmine. Conflating the two shows the author is either ignorant and thus unqualified to talk about the subject matter or tries to mislead the reader. A premine means the public is excluded from mining, which provably never happened in Dash, thus the term is 100% inapplicable.
According to Dash’s founder, Evan Duffield, this premine was the result of a bug. However, there are many people who beg to differ.
Those who "beg to differ" are idiots plain and simple. Because we have already proven that the same thing happened 2.5 years earlier in Litecoin from which Dash originally forked off (and not from Bitcoin as the author initially claims at the beginning of the article).
To ‘resolve’ the situation, the majority of these instamined coins were sold for very low prices on exchanges. However, it is widely believed that most of these coins were simply scooped up by Evan Duffield and the Dash core team for incredibly low prices.
This is my favorite part, because it's probably the only original thought in the article, as I have never heard anyone make up something so incoherently dumb with regards to Dash's launch.
First they say, Evan mined "all the coins by himself" now suddenly he's buying coins for "incredibly low prices"?! So, which is it? Can't have it both ways. Or did he buy coins from himself?
Let's cut the crap. Is it too hard to simply admit the coins were sold on the free and open market to ANYONE willing to buy them?? Nothing was sold to "resolve" anything.
Anyone, not just Evan and the team, had the chance to buy cheap coins for under a Dollar, which was fair and square, hands down. Those who missed out crying foul today are really just trying too hard. Also Dash Core did not exist in 2014. Again the author shows his ignorance further disqualifying himself.
Duffield released Dash before its intended release date (which means the instamine that occurred can be classified as a premine).
This is a lie. It did not happen as anyone can see on the blockchain. The author is a liar.
Dash’s instamine happened because Dash was launched with a block reward of 500 coins per block before it was abruptly cut 2 days later after 2million coins were instamined.
Of course the fix would happen "abruptly" as soon as the necessary blockheight was reached, otherwise it would've gone on forever. It was a mess up and nobody denies this. The fact remains that the coins were sold for pennies as my analysis has shown. Here Evan talks about the launch himself. He clearly states that coins were spilt out too fast and he was under immense pressure to fix it asap.
Initially, Dash was only minable on Linux, which could have been intended so that fewer people would mine Dash and Duffield and Dash’s core team could dominate mining (over 90% of all computers use the Windows operating system).
Conjecture without a shred of evidence assuming ill-intent over good faith. Back in 2014 mining was still a niche hobby by nerds where Linux was the dominating operating system. Evan is a nerd who was using Linux at the time. He didn't own a Windows machine. If he did, why would he offer a reward to someone compiling a Windows binary? If he was the evil fastminer everyone accuses him of, it would be in his best interest to delay Windows mining as much as possible. The accusation holds no water.
Evan Duffield was able to temporarily mine Dash by himself for a while when the public miner wasn't working.
Lie. Lie. Lie. This never happened and the author is still a liar. I know what this alludes to and I have thoroughly debunked it as the nonsense it is.
Dash was initially meant to have a max supply of 80 million DASH, but Evan Duffield held an obscure poll where the majority of the voters voted to reduce the Dash max coin supply from 80million to 20million (which instantly made the instamined DASH worth more).
First of all the value of all coins goes up with a lower supply, not just those that were first mined (duh!). This is intellectual dishonesty, but hardly surprising considering the previous lies of the author. Second, this poll is near worthless as a historic summary as it ignores what went down in the community before: Watch this analysis by Tao of Satoshi to learn that there was major community pressure on Evan's back with endless debates on how to change the reward structure and emission rate of Dash until it was finally settled after a full 7 adjustments in both directions. The narrative that there was one evil singular supply decrease to maliciously enrich Evan is completely stupid.
All in all, Dash’s launch is shrouded in controversy, and it's clear that Evan Duffield and Dash developers benefited tremendously from how everything went down.
The only thing shrouded in mystery is why anyone would believe these false conclusions, accusations and flat out lies when the facts are readily accessible. Of course the founder of any cryptocurrency benefits the most. It's how it's supposed to be. Satoshi "benefitted tremendously" as well from launching Bitcoin. The fact that Evan was able to quit his day job and work for Dash full time was the best thing that could have ever happened to this project. Of course our detractors don't like that, because they don't want to see Dash succeed. But we did and we're still here after 6 years of ceaseless innovation. Repeating ancient lies cannot undo that.
submitted by Basilpop to dashpay [link] [comments]

Reddcoin (RDD) 02/20 Progress Report - Core Wallet v3.1 Evolution & PoSV v2 - Commits & More Commits to v3.1! (Bitcoin Core 0.10, MacOS Catalina, QT Enhanced Speed and Security and more!)

Reddcoin (RDD) Core Dev Team Informal Progress Report, Feb 2020 - As any blockchain or software expert will confirm, the hardest part of making successful progress in blockchain and crypto is invisible to most users. As developers, the Reddcoin Core team relies on internal experts like John Nash, contributors offering their own code improvements to our repos (which we would love to see more of!) and especially upstream commits from experts working on open source projects like Bitcoin itself. We'd like tothank each and everyone who's hard work has contributed to this progress.
As part of Reddcoin's evolution, and in order to include required security fixes, speed improvements that are long overdue, the team has up to this point incorporated the following code commits since our last v3.0.1 public release. In attempting to solve the relatively minor font display issue with MacOS Catalina, we uncovered a complicated interweaving of updates between Reddcoin Core, QT software, MacOS SDK, Bitcoin Core and related libraries and dependencies that mandated we take a holistic approach to both solve the Catalina display problem, but in doing so, prepare a more streamlined overall build and test system, allowing the team to roll out more frequent and more secure updates in the future. And also to include some badly needed fixes in the current version of Core, which we have tentatively labeled Reddcoin Core Wallet v3.1.
Note: As indicated below, v3.1 is NOT YET AVAILABLE FOR DOWNLOAD BY PUBLIC. We wil advise when it is.
The new v3.1 version should be ready for internal QA and build testing by the end of this week, with luck, and will be turned over to the public shortly thereafter once testing has proven no unexpected issues have been introduced. We know the delay has been a bit extended for our ReddHead MacOS Catalina stakers, and we hope to have them all aboard soon. We have moved with all possible speed while attempting to incorproate all the required work, testing, and ensuring security and safety for our ReddHeads.
Which leads us to: PoSV v2 activation and the supermajority on Mainnet at the time of this writing has reached 5625/9000 blocks or 62.5%. We have progressed quite well and without any reported user issues since release, but we need all of the community to participate! This activation, much like the funding mechanisms currently being debated by BCH and others, and employed by DASH, will mean not only a catalyst for Reddcoin but ensure it's future by providing funding for the dev team. As a personal plea from the team, please help us support the PoSV v2 activation by staking your RDD, no matter how large or small your amount of stake.
Every block and every RDD counts, and if you don't know how, we'll teach you! Live chat is fun as well as providing tech support you can trust from devs and community ReddHead members. Join us today in staking and online and collect some RDD "rain" from users and devs alike!
If you're holding Reddcoin and not staking, or you haven't upgraded your v2.x wallet to v3.0.1 (current release), we need you to help achieve consensus and activate PoSV v2! For details, see the pinned message here or our website or medium channel. Upgrade is simple and takes moments; if you're nervous or unsure, we're here to help live in Telegram or Discord, as well as other chat programs. See our website for links.
Look for more updates shortly as our long-anticipated Reddcoin Payment Gateway and Merchant Services API come online with point-of-sale support, as we announce the cross-crypto-project Aussie firefighter fundraiser program, as well as a comprehensive update to our development roadmap and more.
Work has restarted on ReddID and multiple initiatives are underway to begin educating and sharing information about ReddID, what it is, and how to use it, as we approach a releasable ReddID product. We enthusiastically encourage anyone interested in working to bring these efforts to life, whether writers, UX/UI experts, big data analysts, graphic artists, coders, front-end, back-end, AI, DevOps, the Reddcoin Core dev team is growing, and there's more opportunity and work than ever!
Bring your talents to a community and dev team that truly appreciates it, and share the Reddcoin Love!
And now, lots of commits. As v3.1 is not yet quite ready for public release, these commits have not been pushed publicly, but in the interests of sharing progress transparently, and including our ReddHead community in the process, see below for mind-numbing technical detail of work accomplished.
e5c143404 - - 2014-08-07 - Ross Nicoll - Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope. *99a7dba2e - - 2014-08-15 - Cory Fields - tests: fix test-runner for osx. Closes ##4708 *8c667f1be - - 2014-08-15 - Cory Fields - build: add funcs.mk to the list of meta-depends *bcc1b2b2f - - 2014-08-15 - Cory Fields - depends: fix shasum on osx < 10.9 *54dac77d1 - - 2014-08-18 - Cory Fields - build: add option for reducing exports (v2) *6fb9611c0 - - 2014-08-16 - randy-waterhouse - build : fix CPPFLAGS for libbitcoin_cli *9958cc923 - - 2014-08-16 - randy-waterhouse - build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix. *342aa98ea - - 2014-08-07 - Cory Fields - build: fix automake warnings about the use of INCLUDES *46db8ad51 - - 2020-02-18 - John Nash - build: add build.h to the correct target *a24de1e4c - - 2014-11-26 - Pavel Janík - Use complete path to include bitcoin-config.h. *fd8f506e5 - - 2014-08-04 - Wladimir J. van der Laan - qt: Demote ReportInvalidCertificate message to qDebug *f12aaf3b1 - - 2020-02-17 - John Nash - build: QT5 compiled with fPIC require fPIC to be enabled, fPIE is not enough *7a991b37e - - 2014-08-12 - Wladimir J. van der Laan - build: check for sys/prctl.h in the proper way *2cfa63a48 - - 2014-08-11 - Wladimir J. van der Laan - build: Add mention of --disable-wallet to bdb48 error messages *9aa580f04 - - 2014-07-23 - Cory Fields - depends: add shared dependency builder *8853d4645 - - 2014-08-08 - Philip Kaufmann - [Qt] move SubstituteFonts() above ToolTipToRichTextFilter *0c98e21db - - 2014-08-02 - Ross Nicoll - URLs containing a / after the address no longer cause parsing errors. *7baa77731 - - 2014-08-07 - ntrgn - Fixes ignored qt 4.8 codecs path on windows when configuring with --with-qt-libdir *2a3df4617 - - 2014-08-06 - Cory Fields - qt: fix unicode character display on osx when building with 10.7 sdk *71a36303d - - 2014-08-04 - Cory Fields - build: fix race in 'make deploy' for windows *077295498 - - 2014-08-04 - Cory Fields - build: Fix 'make deploy' when binaries haven't been built yet *ffdcc4d7d - - 2014-08-04 - Cory Fields - build: hook up qt translations for static osx packaging *25a7e9c90 - - 2014-08-04 - Cory Fields - build: add --with-qt-translationdir to configure for use with static qt *11cfcef37 - - 2014-08-04 - Cory Fields - build: teach macdeploy the -translations-dir argument, for use with static qt *4c4ae35b1 - - 2014-07-23 - Cory Fields - build: Find the proper xcb/pcre dependencies *942e77dd2 - - 2014-08-06 - Cory Fields - build: silence mingw fpic warning spew *e73e2b834 - - 2014-06-27 - Huang Le - Use async name resolving to improve net thread responsiveness *c88e76e8e - - 2014-07-23 - Cory Fields - build: don't let libtool insert rpath into binaries *18e14e11c - - 2014-08-05 - ntrgn - build: Fix windows configure when using --with-qt-libdir *bb92d65c4 - - 2014-07-31 - Cory Fields - test: don't let the port number exceed the legal range *62b95290a - - 2014-06-18 - Cory Fields - test: redirect comparison tool output to stdout *cefe447e9 - - 2014-07-22 - Cory Fields - gitian: remove unneeded option after last commit *9347402ca - - 2014-07-21 - Cory Fields - build: fix broken boost chrono check on some platforms *c9ed039cf - - 2014-06-03 - Cory Fields - build: fix whitespace in pkg-config variable *3bcc5ad37 - - 2014-06-03 - Cory Fields - build: allow linux and osx to build against static qt5 *01a44ba90 - - 2014-07-17 - Cory Fields - build: silence false errors during make clean *d1fbf7ba2 - - 2014-07-08 - Cory Fields - build: fix win32 static linking after libtool merge *005ae2fa4 - - 2014-07-08 - Cory Fields - build: re-add AM_LDFLAGS where it's overridden *37043076d - - 2014-07-02 - Wladimir J. van der Laan - Fix the Qt5 build after d95ba75 *f3b4bbf40 - - 2014-07-01 - Wladimir J. van der Laan - qt: Change serious messages from qDebug to qWarning *f4706f753 - - 2014-07-01 - Wladimir J. van der Laan - qt: Log messages with type>QtDebugMsg as non-debug *98e85fa1f - - 2014-06-06 - Pieter Wuille - libsecp256k1 integration *5f1f2e226 - - 2020-02-17 - John Nash - Merge branch 'switch_verification_code' into Build *1f30416c9 - - 2014-02-07 - Pieter Wuille - Also switch the (unused) verification code to low-s instead of even-s. *1c093d55e - - 2014-06-06 - Cory Fields - secp256k1: Add build-side changes for libsecp256k1 *7f3114484 - - 2014-06-06 - Cory Fields - secp256k1: add libtool as a dependency *2531f9299 - - 2020-02-17 - John Nash - Move network-time related functions to timedata.cpp/h *d003e4c57 - - 2020-02-16 - John Nash - build: fix build weirdness after 54372482. *7035f5034 - - 2020-02-16 - John Nash - Add ::OUTPUT_SIZE *2a864c4d8 - - 2014-06-09 - Cory Fields - crypto: create a separate lib for crypto functions *03a4e4c70 - - 2014-06-09 - Cory Fields - crypto: explicitly check for byte read/write functions *a78462a2a - - 2014-06-09 - Cory Fields - build: move bitcoin-config.h to its own directory *a885721c4 - - 2014-05-31 - Pieter Wuille - Extend and move all crypto tests to crypto_tests.cpp *5f308f528 - - 2014-05-03 - Pieter Wuille - Move {Read,Write}{LE,BE}{32,64} to common.h and use builtins if possible *0161cc426 - - 2014-05-01 - Pieter Wuille - Add built-in RIPEMD-160 implementation *deefc27c0 - - 2014-04-28 - Pieter Wuille - Move crypto implementations to src/crypto/ *d6a12182b - - 2014-04-28 - Pieter Wuille - Add built-in SHA-1 implementation. *c3c4f9f2e - - 2014-04-27 - Pieter Wuille - Switch miner.cpp to use sha2 instead of OpenSSL. *b6ed6def9 - - 2014-04-28 - Pieter Wuille - Remove getwork() RPC call *0a09c1c60 - - 2014-04-26 - Pieter Wuille - Switch script.cpp and hash.cpp to use sha2.cpp instead of OpenSSL. *8ed091692 - - 2014-04-20 - Pieter Wuille - Add a built-in SHA256/SHA512 implementation. *0c4c99b3f - - 2014-06-21 - Philip Kaufmann - small cleanup in src/compat .h and .cpp *ab1369745 - - 2014-06-13 - Cory Fields - sanity: hook up sanity checks *f598c67e0 - - 2014-06-13 - Cory Fields - sanity: add libc/stdlib sanity checks *b241b3e13 - - 2014-06-13 - Cory Fields - sanity: autoconf check for sys/select.h *cad980a4f - - 2019-07-03 - John Nash - build: Add a top-level forwarding target for src/ objects *f4533ee1c - - 2019-07-03 - John Nash - build: qt: split locale resources. Fixes non-deterministic distcheck *4a0e46e76 - - 2019-06-29 - John Nash - build: fix version dependency *2f61699d9 - - 2019-06-29 - John Nash - build: quit abusing AMCPPFLAGS *99b60ba49 - - 2019-06-29 - John Nash - build: avoid the use of top and abs_ dir paths *c8f673d5d - - 2019-06-29 - John Nash - build: Tidy up file generation output *5318bce57 - - 2019-06-29 - John Nash - build: nuke Makefile.include from orbit *672a25349 - - 2019-06-29 - John Nash - build: add stub makefiles for easier subdir builds *562b7c5a6 - - 2020-02-08 - John Nash - build: delete old Makefile.am's *066120079 - - 2020-02-08 - John Nash - build: Switch to non-recursive make
Whew! No wonder it's taken the dev team a while! :)
TL;DR: Trying to fix MacOS Catalina font display led to requiring all kinds of work to migrate and evolve the Reddcoin Core software with Apple, Bitcoin and QT components. Lots of work done, v3.1 public release soon. Also other exciting things and ReddID back under active dev effort.
submitted by TechAdept to reddCoin [link] [comments]

#Reddcoin ($RDD) Core Wallet Release 3.0.1 - PosV v2 SuperMajority Consensus Upgrade at 45.6% - Required Upgrade

Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020
Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1
This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads.
It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely.
Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2.
Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md
This is a new major version release of Reddcoin.
Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base.
With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future
With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support.
Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks.
Please report bugs using the issue tracker at github:
https://github.com/reddcoin-project/reddcoin/issues
How to Upgrade
If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux).
Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements 
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log
Blockchain Download:
Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files
3.0.1 changelog
*83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version
Credits
Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
@cryptognasher @techadept @chris @cryptobuze @harmonyq @mindredder @paxtech @Tiago Peralta 
Stake on!!
-Reddcoin (RDD) Core Development Team
submitted by TechAdept to reddCoin [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

[IDEA] [PROPOSAL] Monero Debian (deb) packages / Debian package repository deb.getmonero.org (I can do)

I have the skills to implement this if wanted.
Possible User Experience
This is a proposal, i.e. not implemented yet. Instructions for users, simplified.
How to install monero using apt-get
Download the repository signing key.
wget https://www.getmonero.org/monero.asc
Add the signing key.
sudo apt-key --keyring /etc/apt/trusted.gpg.d/monero.gpg add ~/monero.asc
Add APT repository.
echo "deb https://deb.getmonero.org buster main" | sudo tee /etc/apt/sources.list.d/monero.list
Update your package lists.
sudo apt-get update
Install monero.
sudo apt-get install monero
A few technical implementation details
I would simply grab the binaries provided by getmonero.org, download them, check software (gpg) signatures, put these into deb packages, add these to a repository, and upload the repository.
What I would not do is creating the binaries during package creation. While this is nice to have, it doesn't help user experience and blocks the progress on reaching this goal. See next chapter.
Why simply put the pre-build Monero binaries into a deb package?
1) After bitcoin existing for more than 10 years, being popular and being in Debian unstable (sid) it still never made its way into Debian testing, let alone stable. Reason being explained that a difference in underlying libraries (even just security fixes) during compilation may result in a network split. Binaries compiled during packaging on different versions of Linux distributions might have different libraries that might cause a network fork / chain split.
References:
(Note: above website saying Tags: fixed-upstream is probably a mistake as discussion at bottom says.)
2) The github issue of packaging monero stalled.
3) By shipping the same binaries as provided by getmonero.org reduces the chances of introducing a backdoor.
Many Options
Timeline
Doable quickly. The electrum (bitcoin) AppImage was recently added to a Debian package (binaries-freedom) by me and is now easily installable in Whonix. Pre-installed in testers version of Whonix already.
About Me
I am the founder of Whonix, which I am maintaining at present for more than 7 years.
Whonix (formerly TorBOX) is a Debian GNU/Linux–based security-focused Linux distribution. It aims to provide privacy, security and anonymity on the internet.
You can see an overview of packages I am maintaining on my github profile.
To proof that this forum account adrelanos corresponds the same person maintaining whonix.org, it is added here.
Questions
What happened to, what is the successor of the forum funding system?
submitted by adrelanos to Monero [link] [comments]

Reddcoin on Raspberry Pi

A lot of user asked lately, how to run Reddcoin on the popular Raspberry Pi platform. Raspberry Pi is a cheap ARM computer (using junk leftover chips with 10 year lag in technology) but it has enough RAM and consumes around 5 watts, so its ideal to use it for Reddcoin Staking.
This tutorial is not from me, i take NO RESPONSIBILITY about these binaries or the accuracy. This tutorial is created by cryptoBUZE, a fellow member of the Reddcoin community.
Before attempting to follow this tutorial, do a sudo apt-get update
The following commands must be run to install dependencies:
sudo apt-get install libboost-thread-dev
sudo apt-get install libboost-program-options-dev
sudo apt-get install libboost-filesystem-dev
sudo apt-get install libboost-system-dev
Download and install older libssl version - bitcoin clones are using this glorious and fantastic communist product of openssl so it naturally does not works. Its getting totally incompatible after each relase even with itself. Therefore, you must install this, which is the compatible one with the wallet software (no, you cant even compile the code with the newer one) :
wget http://apt.screenlyapp.com/raspbian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1%2Bdeb8u6_armhf.deb
wget http://apt.screenlyapp.com/raspbian/pool/main/o/openssl/libssl-dev_1.0.1t-1%2Bdeb8u6_armhf.deb
sudo dpkg -i libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb
sudo dpkg -i libssl-dev_1.0.1t-1+deb8u6_armhf.deb
Download the wallet software itself:
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoind
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoin-cli
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoin-qt
chmod +x reddcoin\*
When speaking about compatibility, ARM is similar to x86 if you are running user mode applications. You know that every arm based chip needs a different kernel due to the lack of an unified IO system thankfully for the glorious clueless egoistic communist developers at ARM, who succesfully bankrupted the corporation after 25 or so years, and the company got acquired by the japanese softbank. But in user mode, its sort of backward compatible if you have all the proper libraries installed. This means that this will run on any other newer ARM based machine as well (not just raspberry pi-s, on every other arm stuff, chromebooks, or android phones hacked to work with linux).
submitted by GeriGeriGeri to reddCoin [link] [comments]

The Watering Hole Attack and some Points on making Monero Releases better

Warning: No crypto or other excitement inside.
I've been working on making the way the Monero command line tools are released better. This includes easier recipes for building on Windows, the ability to cross compile to any of the currently supported architectures and operating systems on a Linux, or macOS machine with depends, ensuring that libraries used in Monero do not use proprietary components and making Monero binaries reproducible with gitian.
Then end goal of my project is protecting Monero from a watering hole attack. A watering hole attack describes a class of attacks where a tool or binary that is used by a particular group of people is compromised. There are multiple ways to protect a binary from containing malicious, or unintended bytecode.
Foremost it is important to use dependencies that have been compiled from source during the build process. Dependencies should be taken from a source that publishes them directly. This ensures that no 3rd party distributor (software vendor), like sourceforge, who have a track record of shipping adware with its published binaries, messes with the binary in any way. This also lets you finely choose which version of the dependencies you want to use, to ensure you are patched against any recently discovered vulnerabilities of your dependencies.
In past releases Monero already did a decent job with this. The msys packages for windows and brew packages for mac can all be compiled from source. It is also important for a cryptocurrency that releases can be done as quickly as possible, and released binaries should be updated fast. Recent events have shown us, that the security of Monero greatly relies on getting patches out as quickly as possible.
Releasing patched binaries should not be a process that relies on a single, or a small group of developers all being available the entire time. Especially in a system that should be as anti-fragile as possible, developer up time should not be a guarantee. More people should be able to compile release builds of the Monero software and everybody should be able to verify that the release only contains the compiled source code.
Though the current Makefile in the Monero git repository contains commands like make release-static that should be able to do this, practice has shown that the process is confusing and people end up using wrong versions, or misconfigured dependencies (the good old have you compiled with -fPIC? spiel).
When I currently compile Monero version 0.13, my compiled binaries will be different from the published release binaries on getmonero.org. They will have different checksums, meaning I can not be sure if the binaries distributed there contain altered bytecode, or not. This is, because the tools used are not consistent with producing binaries. They place system paths, timestamps and debug symbols in different places of the bytecode depending on the system used. It is however possible to design systems in a way that produce binaries in a consistent manner. Bitcoin and tor use a system called gitian to achieve this. The process of doing this is called reproducible builds.
Reproducible builds allow many developers to collaborate on a build. Some projects have thresholds, where releases are only made when at least three independent developers have produced binaries with matching checksums. The process also allows users to make sure that the binary released is indeed consistent with the source code by matching checksums with the locally compiled binaries with those of the published binaries. When patches need to be released quickly, binary integrity can be proven at a later stage.
All the steps above already decrease the chance of a watering hole attack.
This scheme is still not perfect though. It requires a lot of manual interaction by both developers and users. Still, it does not eliminate all trust, since dependencies and compilers used still need to be trusted. In the end all it ensures is that binaries are compromised in the same way. Currently, there is research being done into 'Transparent Binaries', which would further improve the build environment and make it much easier for people to verify. Information on this can be found on the mozilla wiki and this paper by Tflow.
submitted by the_charlatan_ to Monero [link] [comments]

The Future of Dalilcoin

My role in the Dalilcoin project was to start the network and ensure it could be used for publishing formal mathematics. The network has been running for over a year now and some formal mathematics has been published into the chain. It is time for me to step back and rely on others to ensure the network continues and hopefully build a community of users and developers.
There were unfortunately few stakers other than me the first year and as a result I had access to many block rewards. I have taken most of these rewards and placed them as bounties on conjectures (the same 186 conjectures described in doc/publishingformalmathematics.md). For each conjecture resolved, the one who proves it can collect between 40 and 174.811 fraenks from bounties. While these conjectures remain open, proving conjectures will be more profitable than staking blocks. (The block reward is 25 fraenks.)
Fortunately there seem to be enough other stakers now, but it is worth repeating: Dalilcoin only accepts blocks staked on top of blocks less than a week old. If no one stakes a block in a week, the chain will be essentially dead without a hard fork.
The project is open source and permissionless. I encourage anyone interested in helping support the network or build the community to take the initiative and do what they can best do to help.
I thought it would be good to leave with a loose list of things that could be done.
The basic linux command line and console interfaces are sufficient to run the network, but there would likely be more participants in the network if there were other interfaces available. It would also help if someone ported Dalilcoin to run under Windows and Mac OS. Finally, up until now I have been unwilling to distribute binaries and have insisted on people compiling for themselves. Someone could create binaries appropriate for various platforms and distribute them.
All announcements and discussion up until now has taken place on the dalilcoin subreddit and the subreddit has de facto played the role of the Dalilcoin website. For new people interested in Dalilcoin a more traditional website would be useful. Also, alternative discussion forums might help grow the community.
Dalilcoin also does not yet have a block explorer website. Block explorers are a major way people who are not part of the network gather information about the network, so the lack of a block explorer is significant. Making a Dalilcoin block explorer would be a more serious endeavour than making a traditional block explorer. Some transactions involve mathematical publications and these mathematical publications should be presented in an accessible way. For example, users should be able to search for theorems, definitions and conjectures and obtain reasonably readable presentations of each.
Dalilcoin 0.2.2 could remain as the standard client for the foreseeable future. If someone is interested in making changes to the client, cloning or forking the github repo would be a good first step. Changes can then be made in the other repo. I do not anticipate processing pull requests in my dalilcoin github repo.
Dalilcoin would probably gain much more exposure if it were added to a traditional exchange, but I would still discourage this. Dalilcoin has the infrastructure to support payment channels. (See doc/paymentchannels.md for details.) Payment channels could be used to do cross chain atomic swaps (so that, say, bitcoin or litecoin could be trustlessly exchanged for dalilcoin fraenks). All that is needed is for a website or some p2p client to support people who want to make such a swap.
Mathematical publications are given to Dalilcoin in a very detailed format intended to be easily parsed by the Dalilcoin client. Writing publications in this way by hand is not realistic. The first set of publications (see doc/pubsrc) was mostly obtained by taking items formalized in Qeditas-Egal and modifying Qeditas-Egal to output the items in Dalilcoin's format. A realistic longterm scenario is to modify a mature interactive theorem prover so that users can make definitions and do proofs in that prover and then the prover will generate the Dalilcoin readable version automatically.
Probably the best theorem prover to use for this purpose would be Isabelle. The set theory from Qeditas-Egal seems to be close to the HOLZF logic in Isabelle. Isabelle-HOLZF could be modified to produce Dalilcoin documents as it processes a corresponding Isabelle theory file. Another reason Isabelle would be a good choice is that Dalilcoin supports proving in different theories. A Dalilcoin theory is specified in simple type theory by giving some base types, some typed constants and some axioms. For each Dalilcoin theory a corresponding Isabelle object logic could be created. After that documents published in the new Dalilcoin theory could be drafted by creating Isabelle theory files that work within the corresponding Isabelle object logic.
Another theorem prover that would provide a reasonable fit is Coq. Coq is written in ocaml and so some of the Dalilcoin code could likely be ported into Coq to easily support printing Coq developments in the format Dalilcoin expects. Another reason Coq would be a natural fit is that Coq uses proof terms and (within a certain sublanguage of Coq) the proof terms of Coq will correspond closely to the proof terms Dalilcoin expects.
... the QED system may help preserve mathematics from corruption. We must remember that mathematics essentially disappeared from Western civilization once, during the dark ages. Could it happen again? We must also remember how unprecedented in the history of mathematics is the clarity, even perfection, that developed in this century in regard to the idea of formal proof, and the foundation of essentially the entirety of known mathematics upon set theory. One can easily imagine corrupting forces that could undermine these achievements. For example, one might suspect that there is already a trend towards believing some recent 'theorems' in physics because they offer some predictive power rather than that they have any meaning, much less rigorous proof, with a possible erosion in established standards of rigor. The QED system could offer an antidote to any such tendency. The standard, impartial answer to the question 'Has it been proved?' could become 'Has it been checked by the QED system?'. Such a mechanical proof checker could provide answers immune to pressures of emotion, fashion, and politics. - The QED Manifesto
Thus, be it understood, to demonstrate a theorem, it is neither necessary nor even advantageous to know what it means. - Henri Poincaré
submitted by aliibrahim80 to dalilcoin [link] [comments]

CRITICAL – ELECTRONEUM NETWORK UPGRADE

As you may be aware our v2.0 network upgrade is planned for 30th May 2018 (block height 307,500). The estimated time of upgrade will be 09:30 UTC. To enable you to continue trading / mining Electroneum it is critical that you update your Electroneum nodes and wallet software in advance of the planned network upgrade. The latest date you should update by is 29th May, however we suggest that you SWITCH NOW as a matter of urgency. All transactions created with the latest RPC and CLI wallets will be accepted after the upgrade block, however if you have any transactions in the mempool that were generated with old versions of the CLI or RPC they will fail and be returned to sender.
Upgrade Overview
This major release is aimed at increasing transaction speed and minimising transaction size, in preparation for mass adoption and an exponential increase in global transactional volume.
Anti- ASIC
Implementation of ASIC resistance.
Transfer Fee Increase
We have increased our base fee from 0.01 ETN to 0.1 ETN.
Reduced Privacy
Disabling RingCT & Mixin privacy features means we can fit significantly more transactions into each block than with them enabled. This means less wait to get a transaction into a block and a leaner blockchain size. Wallets are still private as we will continue to use a new stealth wallet address for every blockchain transaction so there is still significantly more privacy than with Bitcoin or Ethereum, but considerably less privacy than with a privacy focused coin like Monero.
Mempool life to 3 days
During times of high transactional volumes you will now have 3 days for the transaction to complete rather than the current 24 hours period.
2 minute blocks
We are moving from one to two minute blocks which will significantly decrease the chance of an orphan block being created.
Block Reward
We are doubling the block reward to ensure that the daily ETN block reward is unaffected.
Reduce difficulty window
We are reducing the difficulty window to check every 360 blocks to adjust the difficulty every 12 hours (in line with current adjustment period).
What happens if I don’t update my nodes?
Failure to update your nodes in advance of the upgrade on May 30th will result in the following:
You will no longer be able to trade Electroneum
Ways to update your nodes
Method One – Compile from source code
Using our GitHub page (link below). Once compiled override the old binaries with the new ones.
https://github.com/electroneum/electroneum/tree/v2.0.0.0
Method Two – Download binaries
From our GitHub release page (link below). Once downloaded you need to check the ‘checksum’ on the zip files to confirm that they are the official versions. Unzip the new binaries over the old ones.
https://github.com/electroneum/electroneum/releases/tag/v2.0.0.0
Checking you’re up to date
Once completed restart and check that you are running the correct version of the daemon and wallet software using this command:
Linux / Mac./electroneumd –version./electroneum-wallet-cli –version./electroneum-wallet-rpc –version –rpc-bind-port 12345
Windowselectroneumd.exe –versionelectroneum-wallet-cli.exe –versionelectroneum-wallet-rpc.exe –version –rpc-bind-port 12345
These commands should output the following:
Electroneum ‘May 2018’ (v2.0.0.0-31f729a)
Thank you for your continued support for the Electroneum project.
The Electroneum Team
(source: Electroneum Official Blog)
submitted by HueyGTO to Electroneum [link] [comments]

Discord Log from Ravencoin Open Developer Meeting - Oct 5, 2018

joey at 1:57 PM

What kind of transaction types are possible with RVN assets? Is it possible to create an asset that has a set lifetime or self-destruct time?

Tron at 2:00 PM

Not for assets/sub-assets/unique. We might be able to do that with voting tokens.

RavencoinDev at 2:01 PM

Hello Everybody!📷1

SpyderDev at 2:01 PM

Hi boss📷1

[Dev] Blondfrogs at 2:01 PM

SUP📷1

Chatturga at 2:01 PM

^📷1

BruceFenton at 2:01 PM

Probably lots of ways to do a self destruct on second layer as well if desired

russ at 2:01 PM

suuuuuupso what is todays topic?

RavencoinDev at 2:02 PM

Thanks for joining us today. We would like to discuss the current status of the 2.1 release.As well as doing an open Q&A at the end.First though I want to thank everybody that helped get the word out on upgrading to the 2.0.4.1 release!Without that fix being in place and exchanges and pools upgrading we would be having a different conversation today.This community is amazing.

russ at 2:04 PM

we would have ended up like pigeoncoinnot a good look📷2

watsure at 2:05 PM

Hello Mr. God

RavencoinDev at 2:05 PM

Exactly

russ at 2:05 PM

i gave pigeoncoin the pullrequest but they ignored meglad we have competent devs

[Dev] Blondfrogs at 2:05 PM

Everyone, So we are planning on getting out build 2.1 as soon as possible. We are still doing bug fixes, and getting the code hardened for release. There is currently one bug is the asset layer that we are fixing right now, and once that is done we should have a couple days of testing. It would be lovely if the community helped with testing, and we appreciate all of the testing that the community has already done. Once, we have a basic build that is tested, we are going to make a public release and notify the miners and pools.

RavencoinDev at 2:06 PM

Once that bug is addressed a release branch will be created.

russ at 2:06 PM

that duplicate ownership asset bug is nasty

RavencoinDev at 2:06 PM

You should all be able to build that and jump on testnet.

[Dev] Blondfrogs at 2:07 PM

@russ Yeah, didn't see that one. BUt I have a fix right now that seems to be working on my local machine

RavencoinDev at 2:07 PM

We need as much testing help from our devs as possible.

[Dev] Blondfrogs at 2:07 PM

so, I will have that pushed up with the day.

russ at 2:07 PM

nice

[Dev] Blondfrogs at 2:08 PM

Just a reminder, that when the new wallet is published, if you don't update your wallet by the time assets are voting in by the blocks you will fork. So, we are going to try and get the wallet out there as soon as we can so users have weeks to upgrade.

Skan at 2:09 PM

Hey everyone

RavencoinDev at 2:10 PM

Any questions comments about the 2.1 release?

Skan at 2:10 PM

Mojave support?

SpyderDev at 2:10 PM

Yes and no

RavencoinDev at 2:10 PM

Good question SkanRight now that's also an issue with Bitcoin.

SpyderDev at 2:12 PM

The short version for Mojave is that the released binaries will work fine.

Skan at 2:12 PM

Interesting, so is it likely going to be a future upgrade that brings stability?

SpyderDev at 2:12 PM

However, developers should hold off.

RavencoinDev at 2:12 PM

We are currently building on High Sierra

Skan at 2:12 PM

Ok good to know for those who ask

SpyderDev at 2:13 PM

There is an incompatibility with Berkeley db version 4 that causes a segfault on init.

RavencoinDev at 2:13 PM

Or using the build scripts that Under created to build on Linux. Thjanks @Under

[Master] Roshii at 2:13 PM

Looks I'm late to the event

[Dev] Blondfrogs at 2:13 PM

THE MASTER!

RavencoinDev at 2:13 PM

Sorry it's late for you @[Master] Roshii

Skan at 2:14 PM

master roshi is never late, he is simply the turtle hermit

SpyderDev at 2:14 PM

One can upgrade Berkeley-db to the latest version and compile with the --incompatible-bdb and things will run, but there are some unknowns as far as wallet compatibility is concerned.

RavencoinDev at 2:15 PM

Raven will likely follow Bitcoin on Mojave support.

SpyderDev at 2:15 PM

The release binaries are compiled on Linux which we have tested on Mojave, so as long as you aren't compiling binaries go ahead and update to Mojave

RavencoinDev at 2:15 PM

It's a problem they have to solve as well, so...

SpyderDev at 2:15 PM

There is supposed to be a patch to bdb, but so far it isn't working

[Master] Roshii at 2:15 PM

@RavencoinDev it's never late for me.

Skan at 2:15 PM

Ok, and for the devs interested just point them to the berkeley upgrade with some warnings or to Under's scripts?

RavencoinDev at 2:16 PM

Right, the wallet runs just fine on Mojave. It's just a developer issue.

[Master] Roshii at 2:16 PM

If I can say anything it will be : don't update to Mojave

SpyderDev at 2:16 PM

There is a warning note in the docs section for OSX building

RavencoinDev at 2:16 PM

Mojave slowed down @[Master] Roshii and the iOS wallet.

Skan at 2:16 PM

YikesOk good to know, just want to be able to help / point people in the right direction

RavencoinDev at 2:17 PM

Thanks @Skan

SpyderDev at 2:17 PM

There is also an issue with Mojave dark mode and the QT wallet that makes things difficult to read (white on white text). We have a workaround which is to disable dark mode for QT in the plist file.

Skan at 2:17 PM

Ok so this is going to be pretty soon then, right ? Next week, likely?

RavencoinDev at 2:18 PM

Any further Mojave questions?Which @Skan ?

Skan at 2:18 PM

I think that covers it for me2.1 releaseIn order to have weeks to upgrade before main net

RavencoinDev at 2:18 PM

Yes, it is looking like we can work through this last issue with asset re-org very soon.Likely early next week.

Skan at 2:20 PM

Is 2.1 going to have any UI updates ?

RavencoinDev at 2:20 PM

Yes, frogs has more details.

[Dev] Blondfrogs at 2:20 PM

The UI is done. It is currently in the develop2. So if you have built the develop2 branch, you would be looking at the new UI for now.

RavencoinDev at 2:21 PM

There have been other QT designs kicked around and we would love to see more from the community.

[Dev] Blondfrogs at 2:21 PM

Future upgrades to come though. but those won't be mandatory upgrades. Just visual upgrades.

SpyderDev at 2:21 PM

The UI tweaks are subtle, but they make a big difference.

Skan at 2:22 PM

Very cool, I will check out dev2 branch

russ at 2:22 PM

new asset creation UI is awesome

Skan at 2:22 PM

I saw that, I like it. And the longer asset holdings list

RavencoinDev at 2:22 PM

@russ Don't make @[Dev] Blondfrogs head any larger...

russ at 2:23 PM

lol

RavencoinDev at 2:23 PM

Other 2.1 release questions/comments?

Skan at 2:23 PM

Cant think of anything else at the momentThanks!

Hans_Schmidt at 2:23 PM

Is dividend support officially part of 2.1 release? It wasn't intuitive to me how that works.

RavencoinDev at 2:24 PM

No it will be in the next release. However, you could write a script that would provide the same functionality with what will be released in 2.1.

Skan at 2:25 PM

I heard something about Phase 4 being complete already, is that true, and is that in 2.1?

RavencoinDev at 2:25 PM

List all addresses with an asset, loop through sending X raven to each.

Skan at 2:25 PM

Unique assets>

RavencoinDev at 2:25 PM

Yes, Unique assets are complete.(edited)

Tron at 2:25 PM

Dividend support can be done without modifying the protocol. We can add it to a version of the software that can be used by the payer, without requiring others to upgrade.So we did phase 1, 2, 4

Skan at 2:26 PM

Oh wowGreat job everyone!

RavencoinDev at 2:26 PM

Yeah, we're super excited about the use cases that assets and unique assets provide to our develoepers(edited)

Skan at 2:27 PM

Can you tell us anything else about this separate software client? Will it be geared more towards enterprise use in general or will it just be that feature?

RavencoinDev at 2:27 PM

Speaking of, do any of you have a dev project in the works with assets?

russ at 2:27 PM

well its not a separate software client, its a backwards compatible release @Skan(edited)kind of like a softfork if you know what that is

Skan at 2:28 PM

Yeah unique assets will be awesome, actually there's a korean community member planning on issuing them along with silver ravencoinsIf im not mistaken

RavencoinDev at 2:28 PM

That's awesome!

russ at 2:28 PM

@RavencoinDev @Scotty is working on an asset explorerhttp://ravencoin.asset-explorer.net/

RavencoinDev at 2:29 PM

Yes, we've been watching that.

Skan at 2:29 PM

I am working with him on a Korean translation of the whitepaper, x16r whitepaper, and an introduction article so that we can take advantage of our availability in that market📷1

RavencoinDev at 2:29 PM

Super excited to see that mature.

Skan at 2:29 PM

@russ ah ok that makes senseWill there be anything else to that release?

RavencoinDev at 2:30 PM

Thanks @Skan. We want Raven to span the globe.Okay, Open Q&A time.What other questions do you guys have?

Skan at 2:31 PM

This release with rewards capability, will there be anything else added/changed for that version?

Tron at 2:31 PM

It might be released as phase 3, 5, 6.Although it could be released separately, without impacting anything.

Skan at 2:32 PM

Ah ok, so all of these features can be opted-into by someone who wants to take advantage, without cluttering the experience for a basic user

Tron at 2:32 PM

Phase 5 and 6 will be together as it requires a hard-fork.

RavencoinDev at 2:33 PM

Yes, we want to focus on user experience so it's super simple to do what you want to do.

Skan at 2:33 PM

Awesome

russ at 2:33 PM

so is anyone working on RSK yet

[Dev] Blondfrogs at 2:34 PM

We aren't yet.

russ at 2:34 PM

yea im gonna have a look at the code soon

[Master] Roshii at 2:34 PM

Who said ravencoin needs RSK

RavencoinDev at 2:34 PM

It'd be great to have that done by the community.

russ at 2:34 PM

i think some people would like smart contracts @[Master] Roshii

Skan at 2:35 PM

RSK would be great for token distributions

russ at 2:35 PM

the real trick would be getting RSK to recognize assets

Tron at 2:35 PM

RSK, Segwit, Lightning are all on the table, but lower priority than phases 3, 5, 6.

[Master] Roshii at 2:35 PM

This is just like saying let's do what ravencoin does in the old fassion!

russ at 2:35 PM

well not really, smart contracts can do other things

[Master] Roshii at 2:36 PM

What's the RBF status @Tron

Skan at 2:36 PM

Keep us posted russ I think that would be amazingWhen you write smart contracts in RSK what language is it in?

russ at 2:36 PM

solidity i thinlthink

RavencoinDev at 2:36 PM

yes

russ at 2:36 PM

eth contracts also work on RSKso thats a plus

Skan at 2:37 PM

Ok great so we dont even have to work on templates or anything

RavencoinDev at 2:37 PM

Having solidity contracts that interact with Raven assets would open up a lot of possibilities.

Skan at 2:37 PM

I think so too, especially for stuff like tokens in gaming use case📷1

russ at 2:37 PM

i guess it would also help with cross chain atomic swaps too

Skan at 2:37 PM

Yep

RavencoinDev at 2:37 PM

Yes!

russ at 2:38 PM

BTC directly for an asset

Skan at 2:38 PM

sounds like a good product

russ at 2:38 PM

making ICOs easier

Tron at 2:38 PM

Yes, cross-chain atomic swaps would be amazing with user issued assets.

RavencoinDev at 2:39 PM

Other questions?

Skan at 2:40 PM

Smart contract atomic swap erc20token 1:1 for their new RVN counterpart

Hans_Schmidt at 2:40 PM

I believe that every cross-chain atomic swap implementation I have seen requires a trusted federation. That's even true for RSK.

Tron at 2:40 PM

@Skan I like it!

Skan at 2:42 PM

No more questions from me

RavencoinDev at 2:42 PM

Okay, seems that we're winding down on the Q&A.Thank you all for joining us today. I've really liked how this discussion has worked out on Discord.Did anybody miss IRC today?

russ at 2:43 PM

hell no

Hans_Schmidt at 2:43 PM

Like a toothache

russ at 2:43 PM

this was waaay better

RavencoinDev at 2:44 PM

📷

Hans_Schmidtat 2:44 PM

Missed the mems tho

RavencoinDevToday at 2:44 PM

I agree. I was even able to fix my typos.That's right, we had some epic memes last time.Where are you @Pathfinder

Chatturga at 2:45 PM

@Pathfinder Do you have an epic meme for us today?

Skan at 2:45 PM

Meme please

[Master] Roshii at 2:46 PM

Can somebody give @Pathfinder a Master Memer role and color

Chatturga at 2:46 PM

https://i.imgflip.com/2jgpgw.jpg📷📷1📷1

Pathfinder at 2:46 PM

heyayeah, that was my meme for today 📷 ty Chatturga

BruceFenton at 2:46 PM

Good stuff

RavencoinDev at 2:47 PM

Thanks everybody!

[Dev] Blondfrogs at 2:47 PM

peace out

Skan at 2:47 PM

Later!

RavencoinDev at 2:47 PM

Have a great weekend. NH Raven Meetup next week!!!!

Jeroz at 2:47 PM

📷

SpyderDev at 2:47 PM

Thanks guys!

RavencoinDev at 2:47 PM

See you there!

Pathfinder at 2:47 PM

I'll be there! looking forward to seeing folks 📷

Hans_Schmidt at 2:47 PM

See ya in NH

Tron at 2:48 PM

See ya there!

Jeroz at 2:48 PM

Cant make it, but have fun! 📷

RavencoinDev at 2:48 PM

^ did you have a question about tron's Comment?

Jeroz at 2:49 PM

No I was super excited about it

RavencoinDev at 2:49 PM

Ah, me too!

russ at 2:49 PM

mtarget is streaming the meetup, right?

RavencoinDev at 2:50 PM

Not sure, we have really appreciated his work in the past but haven't heard.

Chatturga at 2:52 PM

Yes, he is planning on doing a stream📷1

RavencoinDev at 2:53 PM

Thanks again everybody.
submitted by Chatturga to Ravencoin [link] [comments]

Creating a Headless Staking Node on Ubuntu 18.04

Creating a Headless Staking Node on Ubuntu 18.04
##UPDATE## Step 8 - Option 2, has some bugs in the final build process. i haven't had time to work them out yet!

This guide will take you through building and running a headless x42 Full Node! The OS I am using here is Ubuntu 18.04, this guide picks up from a complete/fresh ubuntu install.
This is meant to setup a staking node and so this guide will run you through building, configuring and setting up staking. It will not cover sending transactions or anything else.
The things we are going to do:
  • Step 1 - Install .net core
  • Step 2 - Download The x42 Node Source & Compile It
  • Step 3 - Setting The x42 Node Up To Run On Boot
  • Step 4 - Setup A New Wallet
  • Step 5 - Configure The x42 Daemon
  • Step 6 - Get Address
  • Step 7 - Check Balance
  • Step 8 - Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node # BROKEN#

Step 1 - Install .net Core

Here is the reference link:
https://dotnet.microsoft.com/download/linux-package-manageubuntu18-04/sdk-current
Register Microsoft Key’s & Install Their repos:
cd /tmp wget -q https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb sudo dpkg -i packages-microsoft-prod.deb sudo add-apt-repository universe sudo apt -y install apt-transport-https sudo apt update sudo apt -y install dotnet-sdk-2.2 
Microsoft collect telemetry data by default, if you are part of the “tin foil hat brigade” you can set the following environment variable to turn it off:
echo "DOTNET_CLI_TELEMETRY_OPTOUT=1" >> /etc/environment 
now you should be at a point where .net core is installed on your system… that wasn’t so hard was it! You can check by running the following command:
dotnet--list-sdks 
The output should look like this:
$ dotnet --list-sdks 2.2.103 [/usshare/dotnet/sdk] 

Step 2 - Download & Compile The x42 Node

This part assumes you have GIT installed, if not:
apt -y install git 
Now to pull down the source and compile it!
cd ~/ git clone https://github.com/x42protocol/X42-FullNode.git # “cd” into the source folder cd X42-FullNode/src/ 
Now .net core uses NuGet for package management, before we compile, we need to pull down all of the required packages.. its as simple as running (this will take a couple of minutes) inside of “X42-FullNode/src/”:
dotnet restore 
now we are ready to compile the source, execute (inside of “X42-FullNode/src/”):
dotnet build --configuration Release 
ignore the yellow warnings, this is just the rosyln compiler having a grumble.. if you get red ones then something went wrong! The “--configuration Release” will strip out all debug symbols and slim things down.. only a little, this optional parameter is not mandatory.
Once this is done everything is built/compiled, you can run the daemon directly from the repository, this can be done by going to:
cd ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1 dotnet x42.x42D.dll 
this will kick off the node, however if you exit SSH at this time it will kill the process! however I always recommend copying out the binaries to a separate folder. This can be done with the following:
mkdir ~/x42node mv ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1/*.* ~/x42node/ 
now we have everything we need to run the node outside the git repository! What we need to do now is run the node and have it create the default x42.conf file.. so
cd ~/x42node dotnet x42.x42D.dll 
feel free to hit “CTRL + C” to exit the application after a couple of seconds, by then the folders/files would have been created at the following path:
~/.x42node/x42/x42Main/ 

Step 3 - Setting The x42 Node Up To Run on Boot

Now we are going to create a service file so our x42 node automatically starts when the system is rebooted.
THINGS TO NOTE ABOUT BELOW.. CHANGE THE ##USER## to the username your currently using as these files are within your home directory!
We need to drop to root for this..
sudo -i cat < /etc/systemd/system/x42node.service [Unit] Description=x42 Node [Service] WorkingDirectory=/home/##USER##/x42node ExecStart=/usbin/dotnet /home/##USER##/x42node/x42.x42D.dll Restart=always # Restart service after 10 seconds if the dotnet service crashes: RestartSec=10 SyslogIdentifier=x42node User=##USER## Environment=ASPNETCORE_ENVIRONMENT=Development [Install] WantedBy=multi-user.target EOF 
To enable the service, run the following (as the root user):
systemctl enable x42node.service 
BOOM.. the node isn’t running yet.. but next time the system restarts it will automatically run!
now lets exit out of root!
exit 
We can now start the node up and begin downloading blocks, by running the following command:
sudo systemctl start x42node.service 
if you want to check its loaded and see some of the output, you can run:
sudo systemctl status x42node.service 
an example of the output:
$ sudo systemctl status x42node.service ● x42node.service - x42 Node Loaded: loaded (/etc/systemd/system/x42node.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-01-24 15:47:55 UTC; 14s ago Main PID: 5456 (dotnet) Tasks: 23 (limit: 1112) CGroup: /system.slice/x42node.service └─5456 /usbin/dotnet /home/darthnoodle/x42node/x42.x42D.dll Jan 24 15:48:09 x42staking x42node[5456]: Batch Size: 0 Mb (0 headers) Jan 24 15:48:09 x42staking x42node[5456]: Cache Size: 0/50 MB Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: =======Mempool======= Jan 24 15:48:09 x42staking x42node[5456]: MempoolSize: 0 DynamicSize: 0 kb OrphanSize: 0 Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' connected (outbound), agent 'x42:1.2.13 (70012)', height 213920 Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' offline, reason: 'Receiving cancelled.'. All node screen output can be found in the /valog/syslog file. 

Step 4 - Setup a New Wallet

With the Node running, we now need to setup and/or restore a wallet!
Everything will be performed through the API’s, however by default these API’s are listening on localhost (127.0.0.1), if you are connecting in remotely then this would be a problem since you cant hit that IP. The solution, SSH TUNNEL!
Execute the following command on your local system:
ssh -L 42220:localhost:42220 @ 
This binds the local port (on your system) with 127.0.0.1:42220 on the remote system, once you have executed the command you can type the following address in your laptop/desktop’s web browser and be able to access the API’s:
http://127.0.0.1:42220/swaggeindex.html 
It should look something like this:
https://preview.redd.it/9lzeg3vob8d21.jpg?width=482&format=pjpg&auto=webp&s=b5d574998816056140d5d6de7b03c56772a892fe
To Create a new wallet, first we have to generate some mnemonic works (e.g. the seed), you can do that by going to the following API:
/api/Wallet/mnemonic 
Hit the “Try it out” button which then prompts you for 2 fields:
https://preview.redd.it/dvbdllfrb8d21.jpg?width=722&format=pjpg&auto=webp&s=766d14bafba6facbcd56d31c63c0012748e682e5
Enter “English” and I would recommend 24 words as this greatly increases the seed strength! Once that is done you hit execute and then scroll down to see the “Response Body”, this should contain the mnemonic which you are going to use to create the wallet! This looks something like below:
https://preview.redd.it/6p4q0rsub8d21.jpg?width=603&format=pjpg&auto=webp&s=44b9265626467a43ca670b134c4d28187f475c2e
THIS IS VERY IMPORTANT, BACKUP THIS MNEMONIC TO A SAFE SECURE LOCATION THAT IS ENCRYPTED!!!
So now we have our mnemonic, its time to generate the wallet, for this we need to use the API:
/api/Wallet/create
There are a number of parameters which are required in order to create a wallet:
WalletCreationRequest{ mnemonic string password* string passphrase* string name* string } 
It should be noted that the password and mnemonic are is the most important parts of this request where the “password” will encrypt the wallet and Is required to unlock it.
  • Hit the “Try it out” button
  • input the necessary data
  • Insert the mnemonic
  • Put a password & passphrase
  • “Name” is what your wallet will be called
It should look something like the following:
https://preview.redd.it/958ttfbxb8d21.jpg?width=603&format=pjpg&auto=webp&s=ce48336436ea4b469b5e87513da802de0bf444ee
Hit “Execute”, the “Loading” sign may spin for a few minutes while the wallet is created… once the wallet has been created the “Response Body” will return the mnemonic you have just used.. we now have a wallet!!
HOWEVER IT IS NOT LOADED INTO THE NODE JUST YET!
This is where we will now jump back out and to configure the node to automatically load the wallet and automatically start staking when it first loads.
AGAIN BACKUP YOUR MNEMONIC AND PASSWORD, MAKE SURE THEY ARE ENCRYPTED AND STORED SOMEWHERE SAFE!

Step 5 - Configure The x42 Daemon

Now we are going to modify the x42.conf file in order to automatically load our wallet and start staking 😊
First things first, lets stop our node by running the following command:
sudo systemctl stop x42node.service 
CD to the following folder and view its contents:
~/.x42node/x42/x42Main ls -lah 
within that folder there should be 2 files you are interested in:
-rw-r--r-- 1 darthnoodle darthnoodle 18K Jan 28 16:01 TestWallet.wallet.json -rw-rw-r-- 1 darthnoodle darthnoodle 3.1K Jan 24 15:25 x42.conf 
So TestWallet.wallet.json is our physical wallet that will be loaded, but for right now we want to modify the x42.conf file.. fire up your favourite text editor (if you use VI you’re a masochist)..
nano x42.conf 
The area we are interested in is the following:
####Miner Settings#### #Enable POW mining. #mine=0 #Enable POS. #stake=0 #The address to use for mining (empty string to select an address from the wallet). #mineaddress= #The wallet name to use when staking. #walletname= #Password to unlock the wallet. #walletpassword= #Maximum block size (in bytes) for the miner to generate. #blockmaxsize=1000000 #Maximum block weight (in weight units) for the miner to generate. #blockmaxweight=1000000 #Enable splitting coins when staking. #enablecoinstakesplitting=1 #Minimum size of the coins considered for staking, in satoshis. #minimumstakingcoinvalue=10000000 #Targeted minimum value of staking coins after splitting, in satoshis. #minimumsplitcoinvalue=10000000000 
Uncomment (remove the #) of the following lines and change their value:
stake=1 (changed to 1) walletname=TestWallet (changed to our Wallet Name) walletpassword=password123 (changed to the wallet password) 
save the file and exit back to the command prompt, now we shall restart the node with the following command:
sudo systemctl status x42node.service 
now the wallet is automatically loaded and ready for action!
YES I KNOW YOU HAVE PUT YOUR PASSWORD IN CLEARTEXT, THIS IS WHERE YOU SHOULD HARDEN YOUR BOX. IF THEY CAN GET TO THE POINT WHERE THEY CAN READ YOUR CONF FILE THEY CAN JUST GRAB YOUR WALLET AND BRUTEFORCE THE PASSWORD.
You can check its loaded by going back to the API and executing the following command:
/Dashboard 
Or execute the following command on the NODE:
curl -X GET "http://127.0.0.1:42220/Dashboard" -H "accept: application/json" 
both will produce the same output, if you scroll to the bottom you should see something like this:
======Wallets====== TestWallet/account 0, Confirmed balance: 0.00000000 Unconfirmed balance: 0.00000000 
This means the wallet is loaded and ready for action!!

Step 6 - Get Addresses

Next thing you are probably going to want is a receive address and to check the balance and TX history.. so lets start with getting an address!
Go to the following API:
/api/Wallet/unusedaddress 
Fill in the Wallet name which is “TestWallet” (in this example) and “account 0” (which is the first/default account):
https://preview.redd.it/ayri5jk0c8d21.jpg?width=602&format=pjpg&auto=webp&s=2d16bbb78da49c0125d24d0834c9454d702cb7a1
Hit execute and you should have an x42 address within the “Response Body”:

https://preview.redd.it/tmc495j3c8d21.jpg?width=349&format=pjpg&auto=webp&s=b00177f66a9e24c980d3c6d4e532a33cbf3fb0bc
BOOM… ok now we can receive funds! 😊

Step 7 - Check TX History

Go to the API and the following call:
/api/Wallet/history 
The 2 fields we are most concerned about are:
https://preview.redd.it/lw194af6c8d21.jpg?width=602&format=pjpg&auto=webp&s=27e264bc008879355ff5b9c50a0a5cb06f16e960
Input the name of the wallet and account you want to view the history of, then hit execute. The other fields can be black. This will return a list of TX’s that the wallet has received:
This should look like the following:
https://preview.redd.it/x1hgargac8d21.jpg?width=585&format=pjpg&auto=webp&s=4fd25f22772f4bcec523a6e82b321ae8146a2c75
There is an easier way of doing this, that doesn’t require you to be connected to your node.. especially if your only interested in viewing your staking rewards… THE EXPLORER!
Access the following URL:
https://explorer.x42.tech/address/ 
this will allow you to easily see all TX’s associated with this address, it should look something like below:
https://preview.redd.it/e480grscc8d21.jpg?width=601&format=pjpg&auto=webp&s=0f8a9ebc7944dfcc73f7df659bd839bb983ba90c
… and your done! By this point your node should be running, staking and you have an easy way to view transactions/rewards 😊


Step 8 - Connect The UI Wallet To A Headless Node

The UI utilises a combination of technologies, however the important part is the code attempts to access the x42 Node API on 127.0.0.1:42220.
So you have 2 options here:
  1. Download the Wallet Installers
  2. Compile The UI Yourselves
Pick the option that best suits you given the pros/cons below:
Option 1 - Pro's/Cons
Pro's
  • If you use the installer, its quick and easy.
Cons
  • This also installs an x42 node on your system which runs when the UI loads.
  • If you dont setup an SSH tunnel before running the wallet the local node will bind to the port and the tunnel wont work.. you will be connecting to the local wallet!!
Option 2 - Pro's/Cons
Pro's
  • You only run the UI, the x42 node is not installed
  • you dont have a superfluous node running, downloading blocks on your local system
Cons
  • Time Consuming
  • Have to download dependencies and manually compile the code

Pre-Requirement - Needed For Both Options!!
As previously mentioned, the UI attempts to access the API's on 127.0.0.1:42220, however our node isnt running on our local system. IN ORDER TO GET IT WORKING YOU NEED TO HAVE AN SSH TUNNEL, THIS TUNNEL NEEDS TO REMAIN ACTIVE WHENEVER YOU WANT TO ACCESS THE WALLET.
this can be done by executing the following command:
ssh -L 42220:localhost:42220 @ 


Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node

Download and install the UI/Wallet & Node from:
https://github.com/x42protocol/X42-FullNode-UI/releases

DO NOT RUN THE WALLET YET!
Those of us who dont want to run a local node and just want the UI, execute the following commands (as an administrator):
cd C:\Program Files\x42 Core\resources\daemon\ ren x42.x42D.exe x42.x42D.exe.bak 
The above is with Windows, if your are in *NIX then locate the daemon and rename it (i will update how to do that/where to find it shortly)
Setup the SSH tunnel as outlined above, Execute the wallet and it will load, however you will see an exception:

https://preview.redd.it/9os5h8q7scd21.jpg?width=550&format=pjpg&auto=webp&s=ac45ed7bc987917142075c61fb486e7d71f820d1
dont worry, this is just the wallet trying to execute/start the x42 node which we dont want, if all works according to plan.. after you click "OK" you should now be presented with the wallet UI and have the option to select what wallet you would like to load:

https://preview.redd.it/hnyt0b4mscd21.jpg?width=958&format=pjpg&auto=webp&s=a47df710a804375d8363ffcd77d1ede2862b9b4d
... DONE!

Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node ###BROKEN

THIS IS STILL A WORK IN PROGRESS, THE ELECTRON BUILD DOESNT WANT TO COMPILE BECAUSE SOME CODE IS MANGLED SOMEWHERE!!

Ok, this is the fun bit! .. we need to install the following dependencies. these instructions are written for a Windows system but it should be easy enough to perform the same on a *NIX system.
Install Dependencies
In order to build the wallet UI, you need to install the following components:
  • git
  • NodeJS
  • Electron Builder
First thing you need to do is install git, so download and install the package:
https://gitforwindows.org/
Next you need to install NodeJS, download and install the package:
https://nodejs.org/en/download/
Next we need to install the node package manager:
npm install npx –verbose 
next we need to make sure we have Visual Studio build tools and Python (2.7) installed, this can be done by executing the following (AS AN ADMINISTRATOR!):
npm install -g --production windows-build-tools 
this will install the necessary tools to build C#/C++ code and python 2.7, this could take some time! When its done you should have something like the following;

https://preview.redd.it/5ekfy5g1kcd21.jpg?width=490&format=pjpg&auto=webp&s=f65196dee6f78f2ececec5ee8b5df1044d68f635

Build & Install - Windows
Create a temp folder to navigate to a folder where you want to download the GIT repository, execute the following command:
git clone https://github.com/x42protocol/X42-FullNode-UI.git 
This will clone the repository into the folder, it will only clone the wallet and not the Node source! now lets CD into the folder and build the UI:
cd X42-FullNode-UI\FullNode.UI npm install 
This will download and install all dependencies (can take a while), at the end you should see something like..

https://preview.redd.it/0zfbfxa8kcd21.jpg?width=601&format=pjpg&auto=webp&s=438d072a6ab2bc7a3d84a8dfe773968acc762bc7
Now the stock UI has a number of third-party libraries which contain some vulnerabilities, being a security conscious person, ive also run:
npm audit fix 
when this is done, we have fixed most of the package vulnerabilities 😊 We also get a complaint about the typescript library being too new for the version of angular in use, so run the following command to install the additional dependency:
npm install [email protected]">=2.4.2 <2.7.0" 
now its time to build the UI, execute the following:
npm run build:prod 
once complete you should see something like the following..

https://preview.redd.it/56vf9zfckcd21.jpg?width=601&format=pjpg&auto=webp&s=31b72daff9ab5001843cba529a7bd38c76fd099d
Next its time to compile the electron binary, it should be noted that the build/package process utilises AppVoyer which is not installed and if you attempt to build right now you will get the following error:
cannot expand pattern "${productName}-v${version}-setup-${os}-${env.arch}.${ext}": env arch is not defined. 
To fix this we need to modify the build file, this is a quick one liner that can do it:
powershell -Command "(gc electron-builder.json) -replace 'env.arch', 'arch' | Out-File electron-builder.json" 
Essentially the offending line for Windows is..
"artifactName": "${productName}-v${version}-setup-${os}-${env.arch}.${ext}" 
The build cannot resolve “env.arch”, so the above one liner replaces “env.arch” with “arch” which works 😊
execute the following command:
npx electron-builder build --windows --x64 
At present i get the following error, no matter what i do.. and ive ran out of time to go hunting about.. if anyone has any ideas on how to fix then please post in here or message me on discord:

https://preview.redd.it/t66rtuqdtcd21.jpg?width=918&format=pjpg&auto=webp&s=a3f1a5ff682586348909c67645ca7ae9454922ff


Happy staking!

If you found this post helpful, then buy me a beer and send a donation to XQXeqrNFad2Uu7k3E9Dx5t4524fBsnEeSw
submitted by D4rthNoodle to x42 [link] [comments]

Version 0.19.0.3 is now available for download.

A new version of Actinium NG-wallet is now available for download. It contains the latest Tor release as well as changes & updates from current Bitcoin.
As always you can find binaries for Win32 and macOS and sources for Linux (check doc folder for compilation instructions)
https://github.com/Actinium-project/Actinium-ng/releases/tag/v0.19.0.3
submitted by brakmic to ActiniumCrypto [link] [comments]

Blockchain booming!First data protocol is open source

On May 22, SCRY.INFO, the well-known blockchain technology team, has been open source the block chain data protocol layer (Scry Data Protocol). Developers can visit the GitHub website to view and download the source code and related documents. This is the first data protocol layer open source in the blockchain industry which pro-vides a variety of possibilities for enterprises and developers inside and outside the industry to develop blockchain data products and drive more universities and enterprises to enter the blockchain industry.
The brief introduction of SCRY.INFO protocol layer
By providing SDK for data exchange through blockchain, developers can more conveniently develop DAPP applications.
It mainly includes the following contents:data encryption and decryption, digital signature, smart contract, event notification, data storage interface, data acquisition and query, digital currency payment, the third-party App payment interface, etc.
The process is as follows:
The data provider writes data and metadata through SDK (data includes static data and dynamic data which have the agreed format; metadata mainly includes data signature, data description and other information); the data demander can find the required data through SDK and obtain the data after paying digital currency. The data verifier becomes one by pledging a certain amount of digital currency to the smart contract. In the process of data exchange, the data demander can initiate the compensable data verification request or transaction arbitration to the smart contract, and the verifier is randomly selected by the smart contract. All participants in the data exchange can score each other in the transactions;The smart contract would record the transaction and scoring information of the participants and generate the reputation evaluation of the participants. The reputation evaluation information can be inquired through SDK.
📷
Protocol layer and components
● Component Framework ---- Dot
Component development rules; there are main contents as following: component definitions, component dependencies, component life-cycles, dependency injection and common base components
● Configuration component----default loading component
Now supports json format, would add toml, yaml, command line support in the future
● Log component ---- default loading compo-nent
Based on the high performance log of Zap
● Binary data component
Implement binary data transactions which are the main functions of the now implemented version v0.1.1
● Dapp components
Provide the user interaction interface component
The original intention of development
SCRY.INFO is the world's first blockchain-based quantifiable data exchange platform for real data storage, validation, sharing, analysis and trading. Based on its built-in smart contracts, SCRY.INFO provides cluster-based smart data validation for distributed users across industries, as well as enables access, tools, transactions and sharing on the SCRY platform. SCRY.INFO also provides smart contractual agreements related to a specific industry/event to market-based customers and developers, which can be applied in a variety of commercial data scenarios in sports, entertainment, agriculture, financial markets and other prediction or trading markets.
Now, SCRY.INFO has been open source the first version of the above content and hopes to enable to provide the valuable tool and interfaces in the blockchain application. SCRY.INFO expects that the data protocol layer can be appreciated by developers, especially for the developer who understands software, products and applications. And they can use the data protocol layer with flexible compiling and reusing rather than only executing its own operation.
In the process of utilization, the developer can help open source products achieve real open source value. Finally, the developers of the development community are the real "product managers" who can make suggestions and improvements about the data protocol layer. Thus, let the tool be truly convenient for developers and save the development and research costs in the application of blockchain.
Thanks & invitations
Thanks to all supports of developers for the open source tool which help product advancement and make the charm of open source dazzling. Now, SCRY.INFO considers that the world top software companies such as Google are constantly open source their own software. More and more governments and organizations (such as the White House, Tesla, Harvard University) adopt open source software like Linux. The most well-known bitcoin code in the blockchain industry is open source and the market value of Bitcoin continues to soar which is even called as Gold 2.0. SCRY.INFO has realized that the blockchain industry is gradually on the right way and the latest product open source results of the blockchain project would be the icing on the cake to the project.
The Scry development team sincerely invites developers to come and realize the interface recall based on your hobbies or business scenario needs. Even if users only apply the privacy protection encryption registered by the user ID or recall the data encryption and decryption functions, SCRY.INFO believes it is also good for the data protocol layer. SCRY.INFO expects more developers to try and put forward their own ideas about SCRY protocol layer.
GitHub link:
Blockchain Data Protocol Layer: https://github.com/scryinfo/dp
Component Dot: https://github.com/scryinfo/dot
The base library: https://github.com/scryinfo/scryg
submitted by StephenCuuuurry to SCRYDDD [link] [comments]

Homelab collective ressources post!

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
 
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
 
Latest Additions
 
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.
User Screenshot Source
yours truly http://imgur.com/a/GhCNH https://github.com/Gabisonfire/dashboard-q
lastditchefrt http://i.imgur.com/5zQdao4.png https://github.com/d4rk22/Network-Status-Page
_SleepingBag_ http://i.imgur.com/Ql9ZM4W.png https://github.com/jsank/homelabdash
NiknakSi https://niknak.org/extras/sysinfo TBA
DainBramaged http://imgur.com/jYNlUEQ https://github.com/gordonturneBigBoard
michaelh4u https://i.imgur.com/XkZwMKj.png https://github.com/michaelh4u/homelabfrontpage
spigotx http://imgur.com/a/1zMht https://github.com/spigotx/HomeLab2
SirMaster https://nicko88.com/ https://github.com/dashbad/plex-server-status
yourofl10 http://imgur.com/a/AyROa TBA
TheBobWiley http://imgur.com/a/oU6d3 https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010 http://i.imgur.com/iwtQcsL.jpg https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L https://i.imgur.com/gqdVM6p.jpg https://github.com/mescon/Muximux
ak_rex http://i.imgur.com/a/RJkrT https://github.com/ak-rex/homelab-dashboard
 
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
 
Some other resources: Custom Monitoring Scripts by 0110010001100010
 
Credits to apt64 for his original post
= Pi specific =
 
= Download Automation =
 
= Virtualization =
 
= Monitoring =
 
= Media Center =
 
= Remote access =
 
= VOIP =
 
= Networking =
 
= File Servers/Storage/RAID =
 
= Cameras =
 
= Documentation =
 
= Dynamic DNS =
 
= Backup =
 
= Creating network diagrams =
 
= Guides =
 
= Misc =
 
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
 
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.
submitted by Gabisonfire to homelab [link] [comments]

Dirty Cow - Linux Kernal Exploit - Malayalam How to build an altcoin or bitcoin on Ubuntu Linux Server Shell compile bash payloads to binary  malware development  தமிழில் 4. Installing Bitcoin Core on Linux How to Install Bitcoin Core Wallet on Ubuntu 16

I downloaded Oracle VM to run Linux on my windows computer to compile a windows executable of bitcoin core. I've had many errors and spent over the last 24 hours downloading, building, and overall troubleshooting to no avail. Considering... How to compile a Bitcoin Full Node on a fresh installation of Kubuntu 18.04 without any Linux experience whatsoever. Preface I recently installed a new SSD so I wouldn’t have to prune on my laptop and figured I’d give creating a tutorial a shot. Wait a second. .exe files are used on Windows, not Linux (your executable file is simply named bitcoin-qt and is probably in /usr/local/bin). Are you wanting to compile a version for Windows computers (that's called cross-compiling), or a version to run on other Linux computers without installing other dependencies (that's called static linking)? The title of your question is misleading. The best OS for compiling any bitcoin variant would clearly be a Linux dist. What you're asking is "What is the recommended OS for compiling a Windows binary for Litecoin." – Todd Chaffee Mar 29 '14 at 10:21 Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+

[index] [16097] [4082] [27376] [16239] [30165] [13517] [28083] [12811] [11081] [29977]

Dirty Cow - Linux Kernal Exploit - Malayalam

Headless installation for alt crypto coin using Ubuntu Linux Server. ... Compiling Bitcoin Core Source Code - 2017 debian/ubuntu/linux with Music - Duration: 23:33. On Linux, compiling VanityGen yourself is required. This tutorial shows you how to do that on Ubuntu 14.04, and how to use the tool itself. ... Compiling Bitcoin Core Source Code - 2017 debian ... hi friends in this video i will show you how to compile a bash payload for android and linux. This is our first video of malware development in tamil. i hope you guys would you enjoy this video ... weevely download link :https://github.com/epinna/weevely3 dirty cow exploit : https://raw.githubusercontent.com/FireFart/dirtycow/master/dirty.c Compile with... Bitcoin Core is the open source client of the bitcoin cryptocurrency. ... Compiling Bitcoin Core Source ... Bitcoin using Linux boot USB and secondary for a cold storage wallet - Duration: 6:20 ...

Flag Counter