Python request module for bitcoin json rpc Edureka Community

Gridcoin "Fern" Release
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.



Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.


Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.


The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog



Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.







As a reminder:









Detailed Changelog

[] 2020-09-03, mandatory, "Fern"





submitted by jamescowens to gridcoin [link] [comments]

Technical: The Path to Taproot Activation

Taproot! Everybody wants to have it, somebody wants to make it, nobody knows how to get it!
(If you are asking why everybody wants it, see: Technical: Taproot: Why Activate?)
(Pedants: I mostly elide over lockin times)
Briefly, Taproot is that neat new thing that gets us:
So yes, let's activate taproot!

The SegWit Wars

The biggest problem with activating Taproot is PTSD from the previous softfork, SegWit. Pieter Wuille, one of the authors of the current Taproot proposal, has consistently held the position that he will not discuss activation, and will accept whatever activation process is imposed on Taproot. Other developers have expressed similar opinions.
So what happened with SegWit activation that was so traumatic? SegWit used the BIP9 activation method. Let's dive into BIP9!

BIP9 Miner-Activated Soft Fork

Basically, BIP9 has a bunch of parameters:
Now there are other parameters (name, starttime) but they are not anywhere near as important as the above two.
A number that is not a parameter, is 95%. Basically, activation of a BIP9 softfork is considered as actually succeeding if at least 95% of blocks in the last 2 weeks had the specified bit in the nVersion set. If less than 95% had this bit set before the timeout, then the upgrade fails and never goes into the network. This is not a parameter: it is a constant defined by BIP9, and developers using BIP9 activation cannot change this.
So, first some simple questions and their answers:

The Great Battles of the SegWit Wars

SegWit not only fixed transaction malleability, it also created a practical softforkable blocksize increase that also rebalanced weights so that the cost of spending a UTXO is about the same as the cost of creating UTXOs (and spending UTXOs is "better" since it limits the size of the UTXO set that every fullnode has to maintain).
So SegWit was written, the activation was decided to be BIP9, and then.... miner signalling stalled at below 75%.
Thus were the Great SegWit Wars started.

BIP9 Feature Hostage

If you are a miner with at least 5% global hashpower, you can hold a BIP9-activated softfork hostage.
You might even secretly want the softfork to actually push through. But you might want to extract concession from the users and the developers. Like removing the halvening. Or raising or even removing the block size caps (which helps larger miners more than smaller miners, making it easier to become a bigger fish that eats all the smaller fishes). Or whatever.
With BIP9, you can hold the softfork hostage. You just hold out and refuse to signal. You tell everyone you will signal, if and only if certain concessions are given to you.
This ability by miners to hold a feature hostage was enabled because of the miner-exit allowed by the timeout on BIP9. Prior to that, miners were considered little more than expendable security guards, paid for the risk they take to secure the network, but not special in the grand scheme of Bitcoin.

Covert ASICBoost

ASICBoost was a novel way of optimizing SHA256 mining, by taking advantage of the structure of the 80-byte header that is hashed in order to perform proof-of-work. The details of ASICBoost are out-of-scope here but you can read about it elsewhere
Here is a short summary of the two types of ASICBoost, relevant to the activation discussion.
Now, "overt" means "obvious", while "covert" means hidden. Overt ASICBoost is obvious because nVersion bits that are not currently in use for BIP9 activations are usually 0 by default, so setting those bits to 1 makes it obvious that you are doing something weird (namely, Overt ASICBoost). Covert ASICBoost is non-obvious because the order of transactions in a block are up to the miner anyway, so the miner rearranging the transactions in order to get lower power consumption is not going to be detected.
Unfortunately, while Overt ASICBoost was compatible with SegWit, Covert ASICBoost was not. This is because, pre-SegWit, only the block header Merkle tree committed to the transaction ordering. However, with SegWit, another Merkle tree exists, which commits to transaction ordering as well. Covert ASICBoost would require more computation to manipulate two Merkle trees, obviating the power benefits of Covert ASICBoost anyway.
Now, miners want to use ASICBoost (indeed, about 60->70% of current miners probably use the Overt ASICBoost nowadays; if you have a Bitcoin fullnode running you will see the logs with lots of "60 of last 100 blocks had unexpected versions" which is exactly what you would see with the nVersion manipulation that Overt ASICBoost does). But remember: ASICBoost was, at around the time, a novel improvement. Not all miners had ASICBoost hardware. Those who did, did not want it known that they had ASICBoost hardware, and wanted to do Covert ASICBoost!
But Covert ASICBoost is incompatible with SegWit, because SegWit actually has two Merkle trees of transaction data, and Covert ASICBoost works by fudging around with transaction ordering in a block, and recomputing two Merkle Trees is more expensive than recomputing just one (and loses the ASICBoost advantage).
Of course, those miners that wanted Covert ASICBoost did not want to openly admit that they had ASICBoost hardware, they wanted to keep their advantage secret because miners are strongly competitive in a very tight market. And doing ASICBoost Covertly was just the ticket, but they could not work post-SegWit.
Fortunately, due to the BIP9 activation process, they could hold SegWit hostage while covertly taking advantage of Covert ASICBoost!

UASF: BIP148 and BIP8

When the incompatibility between Covert ASICBoost and SegWit was realized, still, activation of SegWit stalled, and miners were still not openly claiming that ASICBoost was related to non-activation of SegWit.
Eventually, a new proposal was created: BIP148. With this rule, 3 months before the end of the SegWit timeout, nodes would reject blocks that did not signal SegWit. Thus, 3 months before SegWit timeout, BIP148 would force activation of SegWit.
This proposal was not accepted by Bitcoin Core, due to the shortening of the timeout (it effectively times out 3 months before the initial SegWit timeout). Instead, a fork of Bitcoin Core was created which added the patch to comply with BIP148. This was claimed as a User Activated Soft Fork, UASF, since users could freely download the alternate fork rather than sticking with the developers of Bitcoin Core.
Now, BIP148 effectively is just a BIP9 activation, except at its (earlier) timeout, the new rules would be activated anyway (instead of the BIP9-mandated behavior that the upgrade is cancelled at the end of the timeout).
BIP148 was actually inspired by the BIP8 proposal (the link here is a historical version; BIP8 has been updated recently, precisely in preparation for Taproot activation). BIP8 is basically BIP9, but at the end of timeout, the softfork is activated anyway rather than cancelled.
This removed the ability of miners to hold the softfork hostage. At best, they can delay the activation, but not stop it entirely by holding out as in BIP9.
Of course, this implies risk that not all miners have upgraded before activation, leading to possible losses for SPV users, as well as again re-pressuring miners to signal activation, possibly without the miners actually upgrading their software to properly impose the new softfork rules.

BIP91, SegWit2X, and The Aftermath

BIP148 inspired countermeasures, possibly from the Covert ASiCBoost miners, possibly from concerned users who wanted to offer concessions to miners. To this day, the common name for BIP148 - UASF - remains an emotionally-charged rallying cry for parts of the Bitcoin community.
One of these was SegWit2X. This was brokered in a deal between some Bitcoin personalities at a conference in New York, and thus part of the so-called "New York Agreement" or NYA, another emotionally-charged acronym.
The text of the NYA was basically:
  1. Set up a new activation threshold at 80% signalled at bit 4 (vs bit 1 for SegWit).
    • When this 80% signalling was reached, miners would require that bit 1 for SegWit be signalled to achive the 95% activation needed for SegWit.
  2. If the bit 4 signalling reached 80%, increase the block weight limit from the SegWit 4000000 to the SegWit2X 8000000, 6 months after bit 1 activation.
The first item above was coded in BIP91.
Unfortunately, if you read the BIP91, independently of NYA, you might come to the conclusion that BIP91 was only about lowering the threshold to 80%. In particular, BIP91 never mentions anything about the second point above, it never mentions that bit 4 80% threshold would also signal for a later hardfork increase in weight limit.
Because of this, even though there are claims that NYA (SegWit2X) reached 80% dominance, a close reading of BIP91 shows that the 80% dominance was only for SegWit activation, without necessarily a later 2x capacity hardfork (SegWit2X).
This ambiguity of bit 4 (NYA says it includes a 2x capacity hardfork, BIP91 says it does not) has continued to be a thorn in blocksize debates later. Economically speaking, Bitcoin futures between SegWit and SegWit2X showed strong economic dominance in favor of SegWit (SegWit2X futures were traded at a fraction in value of SegWit futures: I personally made a tidy but small amount of money betting against SegWit2X in the futures market), so suggesting that NYA achieved 80% dominance even in mining is laughable, but the NYA text that ties bit 4 to SegWit2X still exists.
Historically, BIP91 triggered which caused SegWit to activate before the BIP148 shorter timeout. BIP148 proponents continue to hold this day that it was the BIP148 shorter timeout and no-compromises-activate-on-August-1 that made miners flock to BIP91 as a face-saving tactic that actually removed the second clause of NYA. NYA supporters keep pointing to the bit 4 text in the NYA and the historical activation of BIP91 as a failed promise by Bitcoin developers.

Taproot Activation Proposals

There are two primary proposals I can see for Taproot activation:
  1. BIP8.
  2. Modern Softfork Activation.
We have discussed BIP8: roughly, it has bit and timeout, if 95% of miners signal bit it activates, at the end of timeout it activates. (EDIT: BIP8 has had recent updates: at the end of timeout it can now activate or fail. For the most part, in the below text "BIP8", means BIP8-and-activate-at-timeout, and "BIP9" means BIP8-and-fail-at-timeout)
So let's take a look at Modern Softfork Activation!

Modern Softfork Activation

This is a more complex activation method, composed of BIP9 and BIP8 as supcomponents.
  1. First have a 12-month BIP9 (fail at timeout).
  2. If the above fails to activate, have a 6-month discussion period during which users and developers and miners discuss whether to continue to step 3.
  3. Have a 24-month BIP8 (activate at timeout).
The total above is 42 months, if you are counting: 3.5 years worst-case activation.
The logic here is that if there are no problems, BIP9 will work just fine anyway. And if there are problems, the 6-month period should weed it out. Finally, miners cannot hold the feature hostage since the 24-month BIP8 period will exist anyway.

PSA: Being Resilient to Upgrades

Software is very birttle.
Anyone who has been using software for a long time has experienced something like this:
  1. You hear a new version of your favorite software has a nice new feature.
  2. Excited, you install the new version.
  3. You find that the new version has subtle incompatibilities with your current workflow.
  4. You are sad and downgrade to the older version.
  5. You find out that the new version has changed your files in incompatible ways that the old version cannot work with anymore.
  6. You tearfully reinstall the newer version and figure out how to get your lost productivity now that you have to adapt to a new workflow
If you are a technically-competent user, you might codify your workflow into a bunch of programs. And then you upgrade one of the external pieces of software you are using, and find that it has a subtle incompatibility with your current workflow which is based on a bunch of simple programs you wrote yourself. And if those simple programs are used as the basis of some important production system, you hve just screwed up because you upgraded software on an important production system.
And well, one of the issues with new softfork activation is that if not enough people (users and miners) upgrade to the newest Bitcoin software, the security of the new softfork rules are at risk.
Upgrading software of any kind is always a risk, and the more software you build on top of the software-being-upgraded, the greater you risk your tower of software collapsing while you change its foundations.
So if you have some complex Bitcoin-manipulating system with Bitcoin somewhere at the foundations, consider running two Bitcoin nodes:
  1. One is a "stable-version" Bitcoin node. Once it has synced, set it up to connect=x.x.x.x to the second node below (so that your ISP bandwidth is only spent on the second node). Use this node to run all your software: it's a stable version that you don't change for long periods of time. Enable txiindex, disable pruning, whatever your software needs.
  2. The other is an "always-up-to-date" Bitcoin Node. Keep its stoarge down with pruning (initially sync it off the "stable-version" node). You can't use blocksonly if your "stable-version" node needs to send transactions, but otherwise this "always-up-to-date" Bitcoin node can be kept as a low-resource node, so you can run both nodes in the same machine.
When a new Bitcoin version comes up, you just upgrade the "always-up-to-date" Bitcoin node. This protects you if a future softfork activates, you will only receive valid Bitcoin blocks and transactions. Since this node has nothing running on top of it, it is just a special peer of the "stable-version" node, any software incompatibilities with your system software do not exist.
Your "stable-version" Bitcoin node remains the same version until you are ready to actually upgrade this node and are prepared to rewrite most of the software you have running on top of it due to version compatibility problems.
When upgrading the "always-up-to-date", you can bring it down safely and then start it later. Your "stable-version" wil keep running, disconnected from the network, but otherwise still available for whatever queries. You do need some system to stop the "always-up-to-date" node if for any reason the "stable-version" goes down (otherwisee if the "always-up-to-date" advances its pruning window past what your "stable-version" has, the "stable-version" cannot sync afterwards), but if you are technically competent enough that you need to do this, you are technically competent enough to write such a trivial monitor program (EDIT: gmax notes you can adjust the pruning window by RPC commands to help with this as well).
This recommendation is from gmaxwell on IRC, by the way.
submitted by almkglor to Bitcoin [link] [comments] a UTXO monitoring methodology and script for true connoisseurs of security, paranoia and BTC maximalism

Disclaimer: the below script is provided for example purposes only. You're responsible for your own security. Don't trust, verify.
tldr: the script is literally just an example wrapper to call "gettxout" on your own node via cron to check if your own utxo has been spent yet
OK, since there are a few questions on security below, let me clarify: this script is only for people who are 1) already running their own nodes and 2) can understand the bash script below. And obviously, don't trust some random person on the internet, always verify. I provided this as an example for a way to monitor your own UTXOs with your existing node. Those of you who understand what the below script does will see it's painfully simple and obviously harmless. Those of you who don't understand it, just ignore this post, or better yet, research what the below means until you do understand it. What's important is the idea of monitoring your own UTXO, and this script is an example of how to do that with gettxout.
Submitting this to help strengthen the community, and for review: a UTXO monitoring methodology and script for true connoisseurs of security, paranoia and BTC maximalism
Monitor canary UTXOs for early detection of compromised private keys BEFORE funds are lost, using your own full node for maximum privacy and trustlessness. Note that you will need to implement your own notification strategy (email, push, sms, etc). This script is intended to run on your full node, but can be run from any machine with RPC access to your full node. is designed to check if a given UTXO (i.e. a specific output of a specific btc transaction) has been spent or not. This can be used for early and proactive detection if a seed phrase or private key has been compromised, so you have time to move your btc before full compromise happens. In order for this to work, a small amount of btc should be sent to an address controlled only by a given seedphrase, with that seedphrase being part of a multisig wallet or a seedphrase+passphrase wallet, and the majority of your funds controlled in the seedphrase+passphrase or multisig wallet. The idea is to leave the small amount of btc (the canary utxo) in the address, so that it never moves unless the seedphrase that controls it has been compromised and all funds in the wallet swept. In this way, you use those compromised sats to buy information about the current security status of your wallet(s).
Example usage:Set up a cron job to run every 30 min to check if transaction output at index "0" for transaction with id "123" has been spent already. Use "my_utxo_nickname" as a friendly name for the UTXO (to differentiate between multiple wallets)
*/30 * * * * /path/to/ 123 0 my_utxo_nickname > /tmp/hodlmon_log 2> /tmp/hodlmon_err_log
Usage scenario #1: Seedphrase (A) + passphrase (A')Majority of funds are held in a wallet controlled by both the seedphrase and passphrase, A and A'. A token amount of btc is controlled only by seedphrase A.
A + A': majority of funds
A: canary UTXO is used to monitor the canary funds locked by A, so that if it is discovered that A has been compromised, the funds locked by A and A' can be moved to a new wallet before the passphrase A' can be cracked and all your funds exfiltrated.
Usage scenario #2: multisig e.g. 2 of 3, with seed phrases A, B and CMajority of funds held in a multisig wallet controlled by 3 seedphrases A, B, and C. 3 small canary UTXOs are held in wallets each controlled by A, B or C, respectively.
A + B + C: majority of funds
A: canary UTXO 1
B: canary UTXO 2
C: canary UTXO 3
One benefit of multisig (e.g. 2 of 3) is that even if 1 key is compromised, your funds are safe, since at least 2 keys are needed to release funds. But how do you that none of the keys has yet been compromised? If you create separate wallets controlled each by only 1 of the individual keys, and use to monitor whether those UTXOs have been exfiltrated, then you can detect partial compromise of your setup before a full exfiltration event takes place, so you can move your funds to a new multisig wallet with freshly generated and uncompromised keys.
Example of 3 cronjobs to monitor all 3 canary UTXOs:
*/30 * * * * /path/to/ 123 0 key1 > /tmp/hodlmon_log_1 2> /tmp/hodlmon_err_log_1
*/30 * * * * /path/to/ 456 0 key2 > /tmp/hodlmon_log_2 2> /tmp/hodlmon_err_log_2
*/30 * * * * /path/to/ 789 0 key3 > /tmp/hodlmon_log_3 2> /tmp/hodlmon_err_log_3

Example hodlmon script:
touch /tmp/hodlmon_last_run
echo "Transaction ID: $1"
echo "Output #: $2"
echo "Nickname: $3"
NODE_IP= #TODO: use actual value
USER=user#TODO: use actual value
PASS=pass #TODO: use actual value
PORT=8332 #TODO: use actual value
CHECK_CMD="/uslocal/bin/bitcoin-cli -rpcconnect=$NODE_IP -rpcuser=$USER -rpcpassword=$PASS -rpcport=$PORT gettxout $1 $2"
echo "${RESULT}"
if [ "$RESULT" == "" ]
MSG="The UTXO for $3 from tx $1 output $2 has moved!"
echo "UTXO is still on ice"

submitted by facepalm5000 to Bitcoin [link] [comments]

WaykiChain (WICC) Monthly Report (September 2020)

WaykiChain (WICC) Monthly Report (September 2020)
Technology & Products
Public Chain Development
· WASM AMPL contract debugging (100%)
· Research on WASM zero-knowledge proof anonymous transfer (50%)
· WASM Sushi contract coding (100%)
· WASM RPC iOS asynchronous library commissioning (100%)
· Verification of the signature push public key algorithm and testing its codability (C++, go) through RPC (100%)
· The new lock-up airdrop contract function: lock-up users can claim the unlocked assets by entering RegID (100%)
· Porting ASWAP contract to public chain 3.0, adding platform fee processing (100%)
· Optimization of Yield Farming contract reward distribution (100%)
· Optimization of Yield Farming contract penalty distribution mechanism (100%)
· Yield Farming contract testing (100%)
· Deployment and initial configuration of WICC and WGRT yield farming contracts and Wayki-X contract completed (100%)
· Ownership of issuance and transfer rights of the bottom-level token ROG transferred to Wayki-X contract (100%)
· The initial generation of ROG completed. 10.08M ROG entered the WICC pool, 2.52M ROG entered the WGRT pool (100%)
· The first 189,000 ROG was minted in Wayki-X contract for rewards by inflation (12.6M × 1.5%) (100%)
· Transfer of 70,000 ROG to AEX for Ecosystem Yield Farming completed (100%)
· WASM developer documentation: added detailed WASM table (Simplified Chinese) (100%)
· WASM developer documentation: added call of multiple contracts and multisignature transactions in WASM contract (Simplified Chinese) (100%)
Application Development
· Yield Farming back end API (100%)
· Yield Farming front end page optimization (100%)
· Yield Farming front end localization (100%)
· Yield Farming pre-release initial API docking (100%)
· Yield Farming application testing (100%)
· Yield Farming application release (100%)
· xUSD & ROG added to Instant in WaykiTimes Android (100%)
· Memory leak issue fixed in Instant in WaykiTimes (100%)
· Data loading error when swiping in Discover fixed in WaykiTimes (100%)
· Data display optimized in Getting Started in WaykiTimes
· UI debugging of several pages in WaykiTimes (100%)
· WaykiTimes 3.0.4 released (100%)
· WaykiTimes Help Center released (100%)
· WaykiTimes Getting Started released (100%)
· WaykiTimes remember password function released (100%)
· WaykiTimes iOS App Store version tested (100%)
· Google crash analysis and testing added to WaykiTimes Android (100%)
· Solved the data loading issue when swiping in Wayki-X Synths (100%)
· Wayki-X price feed delay fixed (100%)
· Amount issue in the plug-in wallet fixed (100%)
· Display error of release contract type of universal transactions fixed on the blockchain explorer (100%)
· WASM contract display specifications for the blockchain explorer completed (100%)
· Development of the Coinbase integration project (wicc-rosetta-api) (85%)
Plan for October
Public Chain Development
· Research on WASM zero-knowledge proof anonymous transfer
· Correction of ASWAP contract proof of liquidity token generation rules
· ASWAP contract testing
· Docking of ASWAP contract with third parties
· Continuous updating of coind RPC interface documentation
Application Development
· Trade — transaction details HTML5 page to native page transfer in WaykiTimes
· Development of the Coinbase integration project (wicc-rosetta-api)
International Market
· On September 4, Russian volunteers opened the second WaykiChain Russian group in Telegram:
· On September 6, WaykiChain opened the official community in Discord:
· On September 6, WaykiChain CTO Richard Chen was invited to the Blockchain + Innovative Service and Industrial Application Conference and the China Chamber of International Commerce Blockchain Innovation Service Industry Committee Establishment Conference as a member of the expert group.
· On September 11, the famous US blockchain TV program Exploring the Block tweeted about WaykiChain, showing it is optimistic about the future development of the integrated DeFi ecology of WaykiChain.
· On September 11, the famous business platform Yahoo Finance released WaykiChain project information and announced that WaykiChain CEO Gordon Gao gives an interview to NASDAQ MarketSite’s Jane King on September 12.
· At 7:00 PM EDT on September 12, world’s largest financial channel Bloomberg TV reported that WaykiChain CEO Gordon Gao was interviewed by Jane King of NASDAQ MarketSite. The interview aired on Fox Business Network at 10:30 PM EDT on September 14.
· On September 12, cryptocurrency Twitter account Crypto Catalog tweeted about WaykiChain, showing it is optimistic about the future development of the integrated DeFi ecology of WaykiChain.
· On September 13, DeFi List added WaykiChain governance token WGRT.
· On September 13, WaykiChain reached market cooperation with the Indian blockchain influencer Gmadvice who started to serve as WaykiChain community manager in India.
· On September 16, WaykiChain released “WaykiChain Launches Phoenix Yield Farming with WICC/WGRT Dual-pool for ROG Genesis Issuance” on Twitter. Up to September 21, the news hit 2,400+ retweets.
· On September 17, the cryptocurrency influencer DeFi List retweeted “WaykiChain Launches Phoenix Yield Farming with WICC/WGRT Dual-pool for ROG Genesis Issuance”.
· On September 18, WaykiChain reached strategic market cooperation with the Korean crypto influencer Pantera who will help WaykiChain establish a broad and strong consensus in Korea.
· On September 19, “WaykiChain Dual-pool ROG Yield Farming Korean Group” community established.
· On September 20, the influencer Crypto Wendy retweeted “WaykiChain Launches Phoenix Yield Farming with WICC/WGRT Dual-pool for ROG Genesis Issuance”.
· On September 21, 130+ Korean media outlets published “WaykiChain Launches Phoenix Yield Farming with WICC & WGRT Dual-pool for ROG Genesis Issuance”.
· On September 23, WaykiChain co-founder and CEO Gordon Gao was invited to an AMA session with ICO Pantera Group, Korea’s top Telegram group (stats by u/combot), where he shared his insights into DeFi with 4,000+ Korean users and introduced WaykiChain’s ROG Genesis Yield Farming.
· On September 24, WaykiChain tweeted “ROG Genesis Yield Farming FAQ” and “Leave your question/problem toward WaykiTimes/Wayki-X/ROG Genesis Yield Farming in the Google forms below to share 800 WICC Giveaway!”, the number of engagements is 1,500+.
· On September 24, WaykiChain global partner Vincent Lionheart was invited to an AMA session to D’va Community.
· On September 24, The Business Telegraph, Bitcoin Garden, and other media published “WaykiChain Launches Phoenix Yield Farming with WICC & WGRT Dual-pool”.
· On September 24, WaykiChain tweeted the ROG Genesis Yield Farming Countdown. The news hit 1,000+ retweets.
· On September 25, ROG Genesis Yield Farming news was the day’s hit in Korea with 5,000+ views on Korean cryptocurrency forums.
National Market
· On September 1, CoinTiger listed WaykiChain governance token WGRT and opened the WGRT/USDT pair. WGRT net buy & hold competition started and the CoinTiger community joined a series of WGRT-themed challenges.
· On September 1, WaykiChain governance token WGRT successfully mapped to Ethereum and ERC-20 WGRT was created. The world’s largest DEX Uniswap officially supported it and listed the WGRT/USDT pair.
· On September 2, WaykiChain Strategic Analyst Jing Tao gave the speech “WGRT Dragon, Fly, Tiger, and Leap: Community Governance Upstart” to the MXC community and distributed 3 gold bars to the event participants.
· On September 7, WaykiChain Strategy Analyst Jing Tao attended [This Is Coin Coffee] live DeFi contest co-sponsored by Coinka,, and WEDEX founder & CEO, Loopring co-founder Chen Xiaoliang and ChainNews Research Director Pan Zhixiong joined the event.
· On September 9, selected WaykiChain governance token WGRT for the Listing Vote. Each voter had a chance to share an airdrop of 420,875.43 WGRT. WGRT passed the voting with 53,293,775 votes and was successfully listed on
· On September 10, WGRT/USDT trading pair and WGRT withdrawals opened on
· On September 10, WaykiChain released WaykiChain Governance Token WGRT Information and Addresses. The team announced that before July 1, 2021, WGRT circulating supply will be strictly controlled at 10% of the total supply, or 2.1 billion.
· On September 9 to 11, WaykiChain was invited to IoT World China & 5G China along with 400+ exhibitors including Huawei, Baidu, and Tencent. WaykiChain demonstrated the integrated public chain DeFi ecosystem that will help China’s digital construction.
· On September 11, WaykiChain Strategy Analyst Jing Tao was invited to the Bepal community and shared the speech “WaykiChain Governance Token WGRT: Accumulation and Breakout”. WaykiChain airdropped 3,000 WGRT and cash red envelopes to the Bepal community members.
· On September 12, WaykiChain Technology & Development Manager Yuanhang Xiao and Strategy Analyst Jing Tao introduced [New WaykiChain DeFi Product: Decentralized Synthetic Asset Issuance Protocol Wayki-X] in the official WaykiChain yizhibo account. During the live broadcast, WaykiChain distributed pure gold bars and branded gifts to lucky users.
· On September 13, WaykiChain co-founder & CEO Gordon Gao and Overseas Director Qiyuan Mei shared the speech “WaykiChain Opens the Era of Integrated DeFi Public Chains” in the live broadcast room. CPO Jiuer was the broadcast host. The guests explained WaykiChain’s DeFi strategy and revealed the launch of Yield Farming.
· On September 15, WaykiChain CEO Gordon Gao and BTC38 co-founder Tianwei Huang held the live stream titled “Eight Questions to Explain DeFi Trends and Opportunities” in yizhibo. The hosts analyzed the status and trends of DeFi, discussed DeFi deployment by public chains and exchanges, and new opportunities in synthetic asset trading. WaykiChain distributed pure gold bars and branded gifts to lucky viewers of the stream.
· On September 16, WaykiChain Strategy Analyst Jing Tao shared the speech titled “WaykiChain’s Integrated DeFi Ecosystem Layout” as the guest of
· On September 18, Bying community invited WaykiChain Strategy Analyst Jing Tao to share the speech “New DeFi Opportunity: Phoenix Yield Farming”. WaykiChain held a WICC airdrop for Bying community members.
· On September 18, WaykiChain published the article “No Pre-mining, ICO, or Reserve! WaykiChain Launches Dual-pool Phoenix Yield Farming”.
· On September 19, WaykiChain published the article “Chapter 1. The Financial Innovation of Blockchain Reformation. The Origin, Logic, and Value of WaykiChain ROG” introducing the background of ROG, the operation mechanism of the decentralized synthetic asset system Wayki-X, and the value foundation of ROG in detail.
· On September 23, “No Pre-mining, ICO, or Reserve! WaykiChain ROG Genesis Farming and Early Release Guide” was released across Chinese media.
· On September 24, WaykiChain CEO Gordon Gao, CTO Richard Chen, and CPO Xi Zhang held a joint live stream on yizhibo explaining the future planning of WaykiChain decentralized synthetic asset issuance protocol Wayki-X, ROG, and WaykiChain DeFi in terms of business model, technology, and products. WaykiChain distributed 1 pure gold bar and 6 branded gifts to the lucky stream viewers.
· On September 24, and WaykiChain launched the WGRT Investment Competition. The prizes are a BMW G 310 R motorcycle, a 13” MacBook Pro, a 10.2” iPad, 17 pure gold bars and 99,000 WGRT.
· On September 25, various Chinese media released “Wayki-X 101: WaykiChain Decentralized Synthetic Asset Protocol” introducing the functions and mechanism of the decentralized synthetic asset issuance protocol Wayki-X and the value of its token ROG in detail.
· On September 25, WaykiChain launched the “Looking for the Genesis Prophet” community event. The winners received 10 branded gifts.
· On September 25, WaykiChain ROG Genesis Yield Farming launched. WICC and WGRT pool quotas (5 million and 25 million, respectively) were full within just one hour.
· On September 25, WaykiChain reached ecosystem partnership with AEX. AEX became the first platform to join ROG Ecosystem Yield Farming.
· On September 25, WaykiChain partnered with Bying wallet. ROG Genesis Yield Farming is available in Bying wallet.
· On September 26, ROG, the main token of WaykiChain’s decentralized synthetic asset issuance protocol Wayki-X, was listed on AEX. ROG/USDT trading pair is available.
· On September 26, WaykiChain CEO Gordon Gao gave lectures “DeFi Financial Principles and Commercial Applications” and “DeFi Industry Panoramic Scan” at The First Offline Practical Training Camp of Hash Power University, Shanghai Station. Participants included Ontology founder Jun Li, Chainlink Labs — China Head Philip Fei, Digital Renaissance Foundation Managing Director Cao Yin, and Waterdrip Capital founding partner Zheng Yushan.
· On September 28, WaykiChain co-founder and CEO Gordon Gao was a guest at Hash Power Knowledge Base Private Meeting, Shenzhen Station where he shared the speech titled “Feasible Ways of DeFi Application Popularization”. Other guests included Ontology founder Jun Li, DeBank founder and CEO Tang Hongbo, and Huobi Research Chief Technical Researcher Tianyuan Ma.
submitted by Waykichain to WICCProject [link] [comments]

Deep fundamental reasons behind all conflicts with Tezos Foundation

Let's first take a look at two core ideas behind Tezos protocol:
  1. In Bitcoin protocol, there are those who create blocks (miners) and users. Those are two fundamentally different groups. As a result of that they do have fundamentally different interests. When those interests are aligned, it's all work very well. However, sometimes those interests might get misaligned. Miners might want one set of changes in the protocol while users might want another set of changes. Tezos procotol solves this problem via proof of stake's baking mechanism by allowing users of XTZ to become block creators (like miners in Bitcoin protocol). Users/holders of XTZ and block creators are now fundamentally the same group and therefore there is no interest misalignment. Moreover, as a consequence of choosing proof of stake over proof of work, almost anyone can become a baker at low cost. Of course, there is a minimum requirement but it can be easily reduced through voting if price XTZ goes too high;
  2. Although per (1) problem of misalignment between users and miners solved, Tezos protocol make one step further. Namely, there is self-amending mechanisms in protocol. Through of the set of voting rounds, attached bounties (via dillution), there is a deterministic path to resolve disputes in upgrading Tezos protocol. Nobody knows the future, nobody knows how protocol should look like after 5-10-20 years. That's why it's very important to have self-amending procedure. Without deterministic path to protocol upgrade, you will have fork-wars like in Bitcoin. As a result of these fork-wars, you now have Bitcoin, Bitcoin Cash, Bitcoin SV. Also, with built-in bounties via dillution, Tezos protocol guarantees funding for its further development;
There is third core idea behind Tezos protocol. Namely, formal verification friendly, low-level and explicit smart contract language - Michelson. While it's very important feature, it's not relevant for this discussion.
Now imagine you are going back in time when Tezos protocol isn't implemented yet, only draft whitepaper. How would you bring it to life if you were original author?
If there were no crypto-currencies, then all you have to do is to take time and implement minimum viable product (MVP) on your own. May be you might do it with co-founder but it's not really necessary for releasing the first version of protocol in absence of any competition.
However, the field was already crowded and time works against you. It would be necessary for project's survival to be as fast as possible in such dynamic field. You need to raise funds to hire dozen of strong programmers to implement Tezos protocol and on top of that to fund development of ecosystem in Tezos network. Namely, wallets, higher-level languages on top of low-level Michelson, education materials for future smart contract writers, new projects similar to 0x, Maker, Compound, Cryptokitties etc.
Now, I would like you to make a pause and think what is Tezos protocol. It tries to align incentives of parties using game-theoretic constructs! And now, I would like you to make second pause and think what crypto-currencies are all about in broader sense. Crypto-currencies are about eliminating centralization and unnecessary middle-mans. One of the biggest middle-mans is governments and their legal system.
People who are in the space for long time should know how much crypto-currencies influenced by Austrian School of Economics (read Hayek's book "Denationalization Of Money" (1976) and early Satoshi Nakamoto's posts).
With that in mind (spirit behind Tezos and crypto-currencies in general), how would you fund development of Tezos protocol and later its initial ecosystem?
The correct answer is to setup decentralized autonomus organization (DAO). Initial DAO on Ethereum protocol since you don't have any Tezos protocol implementations (remember, we are still back in time!).
This DAO will be used to develop Tezos protocol itself and leverage power of smart contracts to correctly align incentives for development of Tezos protocol. Namely, backers of this DAO would get ERC20 token representing voting and governance power. For example, let's say founders raised 250M USD worth in ETH and all of these money will be locked in smart contract. Only backers can unlock funds from smart contract by tranches as Tezos protocol developers making progress. It would be similar to traditional world - seed round, round A, round B etc. When Tezos mainnet goes live, backers would receive proportional amount of XTZ as their ERC20 voting tokens on Ethereum. Since that initial DAO would still have tons of ETH locked by the time Tezos mainnet released, those proceeds will be used to fund wallet developers, high-language developers, and so on (via voting by backers of course).
In this scenario, I would envision that the first big project after Tezos mainnet launched would be to build trustless, decentralized bridge between Tezos blockchain and Ethereum blockchain. Simply, because it would be good to migrate intial DAO and its ETH funds into Tezos blockchain.
There are only two downsides with this approach:
  1. You can't raise funds in Bitcoin but who cares if it's 100M or even 50M (still huge amount of money);
  2. Many people in crypto-space will make fun of you because you just setup DAO on Ethereum while developing Ethereum competitor;
Neither of these two downsides is important. Ultimate upside is that backers has direct control over how funds are spent because they would be the only ones who can unlock funds by voting for proposals.
On meta-level, you would have beautiful symmetry. Namely, you develop Tezos protocol and its ecosystem, using the similar ideas and spirit as Tezos protocol itself!
But we all know that it was never happened!
We all know drama with Gevers who tried to capture power at Tezos Foundation. We all know that there is no RPC command in Tezos github to vote out Tezos Foundation members ;) We all know that we are not in control of Tezos Foundation. Tezos Foundation is a swiss non-profit organization with its own board and we are not part of it. Tezos Foundation is govern under Swiss law and most of you are not even Swiss citizens.
Here is the question why Breitmans suddently decided to throw away all fundamental principles behind crypto-currencies and just went all-in with traditional world? Why we all got stuck with our own mini-Washington, namely Tezos Foundation? There is one reason why Breitmans decided to throw away all their principles and stick with this strange scheme involving Swiss foundations.
The reason is ... socialism. You might think I'm joking but stay with me. There were roaring 1920s and following 1929 stock market crash (by the way that was actually caused by government creating credit bubble). Republican (but still a socialist) Herbert Hoover created depression from 1929 crash. Franklin Roosevelt made this depression truly great! He imposed price-controls and outright gold confiscation (check "Executive Order 6102"). One of his most terrible pieces of paternalistic socialist legislation was "Securities Act of 1933". And this is the reason why Breitmans tried so hard escape iron hand of Roosevelt's zombie.
The same month as Tezos fundraiser, SEC issued statement about the most famous Ethereum DAO:
Basically, they tried to say that DAO violated their 1933 Securities Act (aka Roosevelt zombie). I'm not claiming that Breitmans anticipated this exact SEC statement about Ethereum DAO. All I'm saying that they are smart enough to understand that SEC might come after them as well. It doesn't matter if SEC had right to do so. It doesn't matter that XTZ is not security at all. Only people outside of hardcore old school crypto-community would believe in such non-sense as rights. The truth is that any government is essentially an army which controls a territory and they (not you!) decide what they think is right or wrong.
Breitmans knew that SEC might chase them with bloody machete, so they decided to play traditional game which many played when Switzerland still had numbered accounts. Namely, using Switzerland as old-style traditional escape from Roosevelt zombies.
Unfortunately, for them they got in hands of people who knew too well how actually Swiss foundations work. We all remember how Gevers tried to exploit Swiss law about foundations to seize control over foundation's assets. Now we have new drama. But fundamentally, it's all because Breitmans choose Swiss law over Ethereum smart-contracts.
Don't get me wrong, I'm not blaming Breitmans. I really think that their fear of Roosevelt zombie with bloody machete led them to setup weird foundation in Switzerland. In normal circumstances, I don't see any rational reason not to setup DAO as I described above.
Zooming out, on the bigger scale, you might see that these two worlds (i.e. traditional government law and crypto) are not compatible at all. You just can't have both of two worlds.
For the same reason, I don't believe in STOs. It's a nice toy, a temporary thing to bootstrap your Defi ecosystem in Tezos but nothing more than that.
Every STO, at some point, rely on some centralized entity which is controlled by law of some jurisdiction. Once government (aka army which control territories and make visibility of its own legitimacy via elections and passing laws) decides that your STO is not compliant, all these STO tokens will be worthless overnight. More on this in my another long post:
Regardless of what's happen with Tezos Foundation, I strongly believe that Tezos protocol will thrive. Mainnet went life and the jinn that can't be put back in the bottle!
Update: Many here criticized my position regarding STOs. That's partly my fault with being too lax with terminology (once I wrote big post, I didn't have much energy to clarify on STOs in the end). By STO, I mean any tokens backed by regulated assets (again, I know it's lax definition). I assumed almost everyone here is for open, borderless finance. As a result of that, I assumed that you want to make these tokens available for everyone and that's why one day government will put pressure on such STO issuers to freeze tokens. However, it's turned out that some people excited for STOs being fully regulated from the start and therefore these tokens wouldn't be available for everyone. Basically, some people see main benefits of STOs as being pro-actively censorship friendly. In other words, they want to move all compliance on blockchain. Whereas, I see very existence of government regulations as root of all problems. Having said that, I'm not against STOs but I'm not very excited about them either. You have to make great mental leap to understand that fully-regulated STOs fundamentally solving wrong problem. You have to build fully censorship resistant technology, not fully censorship friendly. No matter how big market for STOs, it's still several orders of magnitude smaller than potential world of fully-inclusive finance without any borders whatsoever. Tezos is very well equipped for this ambitious task especially with new privacy features coming. Remember, Satoshi Nakamoto didn't ask permission from governments before releasing Bitcoin.
submitted by omgcoin to tezos [link] [comments]

Groestlcoin 6th Anniversary Release


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?

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.
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.

Other Linux


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


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.





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.



Main Release (Main Net)
Testnet Release


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.


Live Version (Not Recommended)



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).





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).




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.


Remastered Improvements



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.



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


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.



Linux / OSX (Instructions)


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.



Main Net
Main Net (FDroid)
Test Net


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.




UPDATED – P2Pool Test Net



Pre-Hosted Testnet P2Pool is available via


submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

How can I get this script to work for Litecoin

What would I need to do to get this script to work for Litecoin
 class Bitcoin { // Configuration options private $username; private $password; private $proto; private $host; private $port; private $url; private $CACertificate; // Information and debugging public $status; public $error; public $raw_response; public $response; private $id = 0; /** * @param string $username * @param string $password * @param string $host * @param int $port * @param string $proto * @param string $url */ function __construct($username, $password, $host = 'localhost', $port = 8332, $url = null) { $this->username = $username; $this->password = $password; $this->host = $host; $this->port = $port; $this->url = $url; // Set some defaults $this->proto = $host == 'localhost' ? 'http':'https'; $this->CACertificate = null; } /** * @param string|null $certificate */ function setSSL($certificate = null) { $this->proto = 'https'; // force HTTPS $this->CACertificate = $certificate; } function __call($method, $params) { $this->status = null; $this->error = null; $this->raw_response = null; $this->response = null; // If no parameters are passed, this will be an empty array $params = array_values($params); // The ID should be unique for each call $this->id++; // Build the request, it's ok that params might have any empty array $request = json_encode(array( 'method' => $method, 'params' => $params, 'id' => $this->id )); // Build the cURL session $curl = curl_init("{$this->proto}://{$this->username}:{$this->password}@{$this->host}:{$this->port}/{$this->url}"); $options = array( CURLOPT_RETURNTRANSFER => TRUE, CURLOPT_FOLLOWLOCATION => TRUE, CURLOPT_MAXREDIRS => 10, CURLOPT_HTTPHEADER => array('Content-type: application/json'), CURLOPT_POST => TRUE, CURLOPT_POSTFIELDS => $request ); if ($this->proto == 'https') { // If the CA Certificate was specified we change CURL to look for it if ($this->CACertificate != null) { $options[CURLOPT_CAINFO] = $this->CACertificate; $options[CURLOPT_CAPATH] = DIRNAME($this->CACertificate); } else { // If not we need to assume the SSL cannot be verified so we set this flag to FALSE to allow the connection $options[CURLOPT_SSL_VERIFYPEER] = FALSE; } } curl_setopt_array($curl, $options); // Execute the request and decode to an array $this->raw_response = curl_exec($curl); $this->response = json_decode($this->raw_response, TRUE); //error_log('this->response: '. print_r($this->response,true)); // If the status is not 200, something is wrong $this->status = curl_getinfo($curl, CURLINFO_HTTP_CODE); // If there was no error, this will be an empty string $curl_error = curl_error($curl); curl_close($curl); if (!empty($curl_error)) { $this->error = $curl_error; } if ($this->response['error']) { // If bitcoind returned an error, put that in $this->error $this->error = $this->response['error']['message']; } elseif ($this->status != 200) { // If bitcoind didn't return a nice error message, we need to make our own switch ($this->status) { case 400: $this->error = 'HTTP_BAD_REQUEST'; break; case 401: $this->error = 'HTTP_UNAUTHORIZED'; break; case 403: $this->error = 'HTTP_FORBIDDEN'; break; case 404: $this->error = 'HTTP_NOT_FOUND'; break; } } if ($this->error) { return FALSE; } return $this->response['result']; } } /* Address History Interface Class */ class AddressHistory { public $address = null; public $n_tx = 0; public $total_sent = 0; public $total_received = 0; public $balance = 0; public $final_balance = 0; public $txns = array(); public function __construct($txn=null) { if(! is_array($txn)) return null; if(array_key_exists('address', $txn)) $this->address = $txn['address']; if(array_key_exists('n_tx', $txn)) $this->n_tx = $txn['n_tx']; if(array_key_exists('total_sent', $txn)) $this->total_sent = $txn['total_sent']; if(array_key_exists('total_received', $txn))$this->total_received = $txn['total_received']; if(array_key_exists('balance', $txn)) $this->balance = $txn['balance']; if(array_key_exists('final_balance', $txn)) $this->final_balance = $txn['final_balance']; if(is_array($txn['txns'])) { foreach($txn['txns'] as $key => $this_txn) { $new_txn = array( 'hash' => $this_txn['hash'], 'block_height' => $this_txn['block_height'], 'value' => $this_txn['value'], 'spent' => $this_txn['spent'], 'spent_by' => $this_txn['spent_by'], 'confirmations'=> $this_txn['confirmations'] ); $this->txns[$key] = new TransRef($new_txn); } } else { $this->txns = null; } return $this; } } /* Transaction Reference Interface Class */ class TransRef { public $hash; public $block_height; public $value; public $spent; public $spent_by; public $confirmations; public function __construct($txnref=null) { if(! is_array($txnref)) return null; if(array_key_exists('hash', $txnref)) $this->hash = $txnref['hash']; if(array_key_exists('block_height', $txnref)) $this->block_height = $txnref['block_height']; if(array_key_exists('value', $txnref)) $this->value = $txnref['value']; if(array_key_exists('spent', $txnref)) $this->spent = $txnref['spent']; if(array_key_exists('spent_by', $txnref)) $this->spent_by = $txnref['spent_by']; if(array_key_exists('confirmations', $txnref)) $this->confirmations = $txnref['confirmations']; return $this; } } /* CoindRPC - JsonRPC Class to talk to bitcoind */ class CoindRPC extends Bitcoin { public function __construct() { return parent::__construct(WN_RPC_USER, WN_RPC_PASS, WN_RPC_HOST, WN_RPC_PORT); } public function __call($method, $params) { return parent::__call($method, $params); } public function get_address_balance($address, $confirmations=0) { try { $address_info = $this->validateaddress($address); if($address_info['isvalid'] == 1 && $address_info['ismine'] == 1) { $balance = $this->getreceivedbyaddress($address, $confirmations); } if($balance != '') { return floatval($balance); } else { return 0; } } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } public function get_address_history($address) { try { $address_info = $this->validateaddress($address); if($address_info['isvalid'] == 1 && $address_info['ismine'] == 1) { //- if only listening to one BTC account //$history = $this->listtransactions(WN_RPC_ACCT); $history = $this->listtransactions(); $txns = array(); $final_balance = $balance = 0; foreach($history as $txn) { if($txn['address'] != $address) continue; $n_tx = $total_received = $total_sent = 0; $n_tx = intval($addr_hist['n_tx']) + 1; switch($txn['category']) { case('receive'): $total_received = $addr_hist['total_received'] += $txn['amount']; $balance = $balance + $txn['amount']; //- can we trust final balance here? do we need more history $final_balance = $final_balance + $txn['amount']; break; case('send'): $total_sent = $addr_hist['total_sent'] += $txn['amount']; $balance = $balance + $txn['amount']; //- can we trust final balance here? do we need more history $final_balance = $final_balance + $txn['amount']; break; } $txns[] = array( 'hash' => $txn['txid'], 'value' => $txn['amount'], 'spent' => $txn['spent'], 'spent_by' => $txn['spent_by'], 'confirmations' => $txn['confirmations'], ); } $addr_hist = array( 'address' => $address, 'n_tx' => $n_tx, 'total_sent' => $total_sent, 'total_received' => $total_received, 'balance' => $balance, 'final_balance' => $final_balance, 'txns' => $txns ); $addr_hist = new AddressHistory($addr_hist); } else { $addr_hist = false; error_log('Address invalid: '.$address); error_log('['.__LINE__.'] : '.__FILE__); } return $addr_hist; } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } public function get_transaction($hash) { try { return $this->gettransaction($hash); } catch (Exception $e) { error_log('error: '. print_r($e->getMessage(),true)); error_log('['.__LINE__.'] : '.__FILE__); } } } /* Helper class */ class Helper { public static $api = null; public static $db = null; public function __construct($db, $api) { Helper::$api = $api; Helper::$db = $db; } public static function walletnotify_email($txnhead) { //- bitcoind calls walletnotify on 0 confirmations and 1. //- We only want email to go out on the first call. Otherwise //- if we want only one 1 confrime, change this to //- confirmations == 0) return; if($txnhead['confirmations'] > 0) return; $tmpl = file_get_contents('email.notify.tmpl.html'); foreach($txnhead as $key => $val) { $map['{'.$key.'}'] = $val; } $map['{timestamp}'] = date('Y-m-d H:i:s', WN_GLOBAL_TIMESTAMP); $map['{hostname}'] = php_uname('n'); $html = str_replace(array_keys($map), array_values($map), $tmpl); $txid_short = substr($txnhead['txid'], 0, 4).' .. '.substr($txnhead['txid'], -4); $msg = "=WNotify=". "\ntxid: ".$txid_short. "\nAmt : ".$txnhead['amount']. "\nCmnt: ".$txnhead['comment']. "\nAcct: ".$txnhead['account']. "\nConf: ".$txnhead['confirmations']. "\nCat : ".$txnhead['category']. "\nAddr: ".$txnhead['address']. ""; //- send to carrier's email to SMS gateway if configured if(defined('WN_SMS_ADMIN') && filter_var(WN_SMS_ADMIN, FILTER_VALIDATE_EMAIL)) { Helper::send_email_sms($msg, WN_SMS_ADMIN); } return Helper::send_email($html, 'WN:WalletNotify', WN_EMAIL_ADMIN);; } public static function send_email($msg, $subj, $to) { $headers = 'From: '.WN_EMAIL_FROM."\r\n"; $headers .= "MIME-Version: 1.0\r\n"; $headers .= "Content-Type: text/html; charset=ISO-8859-1\r\n"; if(trim($msg) == '') return false; return mail($to, $subj, $msg, $headers); } public static function send_email_sms($msg, $to) { if(trim($msg) == '') return false; if($to == '') return false; $headers = 'From: '.WN_EMAIL_FROM."\r\n"; return mail($to, null, $msg."\n.", $headers); } } 
submitted by Mjjjokes to cryptodevs [link] [comments]

Daily analysis of cryptocurrencies 20191005(Market index 31 — Fear state)

Daily analysis of cryptocurrencies 20191005(Market index 31 — Fear state)

Attorney General Barr Signs Letter To Facebook From US, UK, And Australian Leaders Regarding Use Of End-To-End Encryption The Department of Justice published an open letter on October 3 to Facebook from international law enforcement partners from the United States, United Kingdom, and Australia in response to the company’s publicly announced plans to implement end-to-end-encryption across its messaging services. The letter is signed by Attorney General William P. Barr, United Kingdom Home Secretary Priti Patel, Australia’s Minister for Home Affairs Peter Dutton, and Acting Homeland Security Secretary Kevin McAleenan. Addressed to Facebook’s CEO, Mark Zuckerberg, the letter requests that Facebook not proceed with its end-to-end encryption plan without ensuring there will be no reduction in the safety of Facebook users and others, and without providing law enforcement court-authorized access to the content of communications to protect the public, particularly child users.
Coincheck Launches New Service That Rewards Gas Users With Bitcoin In an attempt to bring crypto to the mass audience, Japanese crypto exchange Coincheck inked a partnership deal with E-net Systems to reward gas users in the Tokyo Gas area, the company announced Oct 4. Under the partnership agreement, the two companies will start offering Coincheck Gas with two crypto-related plans for its customers. The gas service by the crypto company will offer a Bitcoin Rewards Plan under which customers will receive Bitcoin as rewards for the usage of gas. In addition, customers can also pay their gas bills using Bitcoin under the Bitcoin Payment Plan.
Libra Association: 1500 Entities Have Indicated Enthusiastic Interest To Join Libra After PayPal announced to withdraw their support for Facebook’s Libra cryptocurrency, Libra posted a series of tweets in response to the striking news. Libra Association tweeted: “Building a modern, low-friction, high-security payment network that can empower billions of financially underserved people is a journey, not a destination. This journey to build a generational payment network like the Libra project is not an easy path.” “We recognize that change is hard, and that each organization that started this journey will have to make its own assessment of risks and rewards of being committed to seeing through the change that Libra promises,” they continued. The final tweet read: “We look forward to the first Libra Council meeting in 10 days and will be sharing updates following that, including details of the 1,500 entities that have indicated enthusiastic interest to participate.”
Prysmatic Labs Team Unveils Updates On The Ethereum Serenity Roadmap Prysmatic Labs team has unveiled biweekly updates on the Ethereum Serenity roadmap via Medium. According to the article, the testnet has been restarted for everyone to experience staking and becoming a validator. This testnet includes beacon chain spec v0.8.4, various performance improvements, faster BLS paring library, new syncing strategies and more RPC end point support.
Japan: Using Virtual Currency To Make Donations To Politicians Is Legal Citing Yomiuri Shimbun, the Japanese Ministry of Internal Affairs and Communications, a cabinet-level ministry in the Government of Japan, indicated that the use of virtual currency to donate to politicians is not illegal. According to Japan’s Political Fund Control Law, it is prohibited to conduct donations to politicians in principle, but virtual currency is not in the category of “money and securities” which are covered by law.

Encrypted project calendar(October 05, 2019)

Ontology (ONT): Ony Ji will attend the blockchain event in Japan on October 5th and explain the practical application based on the ontology network. BNB/Binance Coin: The Binance Coin (BNB) Oasis Game Hackathon will be held on October 5th in Bangalore, India, and will be hosted by Binance Labs, Matic Network, Cocos-BCX, Celer Network, Marlin Protocol.

Encrypted project calendar(October 06, 2019)

SPND/ Spendcoin: Spendcoin (SPND) will be online on October 6th

Encrypted project calendar(October 07, 2019)

GNO/Gnosis: Gnosis (GNO) will discuss the topic “Decentralized Trading Agreement Based on Ethereum” will be held in Osaka, Japan on October 7th. Kyber and Uniswap, Gnosis and Loopring will attend and give speeches.

Encrypted project calendar(October 08, 2019)

BTC/Bitcoin: The 2nd Global Digital Mining Summit will be held in Frankfurt, Germany from October 8th to 10th.

Encrypted project calendar(October 09, 2019)

CENNZ/Centrality: Centrality (CENNZ) will meet in InsurTechNZ Connect — Insurance and Blockchain on October 9th in Auckland.

Encrypted project calendar(October 10, 2019)

INB/Insight Chain: The Insight Chain (INB) INB public blockchain main network will be launched on October 10. VET/Vechain: VeChain (VET) will attend the BLOCKWALKS Blockchain Europe Conference on October 10. CAPP/Cappasity: Cappasity (CAPP) Cappasity will be present at the Osaka Global Innovation Forum in Osaka (October 10–11).

Encrypted project calendar(October 11, 2019)

OKB/OKB: OKB (OKB) OKEx series of talks will be held in Istanbul on October 11th to discuss “the rise of the Turkish blockchain.”

Encrypted project calendar(October 12, 2019)

BTC/Bitcoin: The 2019 Global Mining Leaders Summit will be held in Chengdu, China from October 12th to 14th.

Encrypted project calendar(October 14, 2019)

BCH/Bitcoin Cash: The ChainPoint 19 conference will be held in Armenia from October 14th to 15th.

Encrypted project calendar(October 15, 2019)

RUFF/RUFF Token: Ruff will end the three-month early bird program on October 15th KAT/Kambria: Kambria (KAT) exchanges ERC20 KAT for a 10% bonus on BEP2 KAT-7BB, and the token exchange reward will end on October 15. BTC/Bitcoin: The Blockchain Technology Investment Summit (CIS) will be held in Los Angeles from October 15th to 16th.

Encrypted project calendar(October 16, 2019)

BTC/Bitcoin: The 2019 Blockchain Life Summit will be held in Moscow, Russia from October 16th to 17th. MIOTA/IOTA: IOTA (MIOTA) IOTA will host a community event on the theme of “Technology Problem Solving and Testing IoT Devices” at the University of Southern California in Los Angeles on October 16. ETH/Ethereum: Ethereum launches Istanbul (Istanbul) main network upgrade, this main network upgrade involves 6 code upgrades. QTUM/Qtum: Qtum (QTUM) Qtum main network hard fork is scheduled for October 16.

Encrypted project calendar(October 18, 2019)

BTC/Bitcoin: The SEC will give a pass on the VanEck/SolidX ETF on October 18th and make a final decision HB/HeartBout: HeartBout (HB) will officially release the Android version of the HeartBout app on October 18.

Encrypted project calendar(October 19, 2019)

PI/PCHAIN Network: The PCHAIN (PI) backbone (Phase 5, 82 nodes, 164, 023, 802 $ PI, 7 candidates) will begin on October 19. LINK/ChainLink: Diffusion 2019 will be held in Berlin, Germany from October 19th to 20th

Encrypted project calendar(October 21, 2019)

KNC/Kyber Network: The official online hackathon of the Kyber Network (KNC) project will end on October 21st, with more than $42,000 in prize money.

Encrypted project calendar(October 22, 2019)

ZRX/0x: The 0x protocol (ZRX) Pantera blockchain summit will be held on October 22.

Encrypted project calendar(October 23, 2019)

MIOTA/IOTA: IOTA (MIOTA) IOTA will host a community event on October 23rd at the University of Southern California in Los Angeles with the theme “Connecting the I3 Market and Experiencing Purchase and Sales Data.” BTC/Bitcoin: The WBS World Blockchain Summit (Middle East) will be held in Dubai from October 23rd to 24th.

Encrypted project calendar(October 24, 2019)

BCN/Bytecoin: Bytecoin (BCN) released the hidden amount of the Bytecoin block network on October 24.

Encrypted project calendar(October 25, 2019)

ADA/Cardano: Cardano (ADA) The Ada community will host a community gathering in the Dominican Republic for the first time on October 25.

Encrypted project calendar(October 26, 2019)

KAT/Kambria: Kambria (KAT) Kambria will host the 2019 Southern California Artificial Intelligence and Data Science Conference in Los Angeles on October 26th with IDEAS. BTC/Bitcoin: CoinAgenda Global Summit will be held in Las Vegas from October 26th to 28th

Encrypted project calendar(October 28, 2019)

LTC/Litecoin: Litecoin (LTC) 2019 Litecoin Summit will be held from October 28th to October 29th in Las Vegas, USA BTC/Bitcoin: Mt.Gox changes the debt compensation plan submission deadline to October 28 ZEC/Zcash: Zcash (ZEC) will activate the Blossom Agreement on October 28th

Encrypted project calendar(October 29, 2019)

BTC/Bitcoin: The 2nd World Encryption Conference (WCC) will be held in Las Vegas from October 29th to 31st.

Encrypted project calendar(October 30, 2019)

MIOTA/IOTA: IOTA (MIOTA) IOTA will host a community event on October 30th at the University of Southern California in Los Angeles on the topic “How to store data on IOTA Tangle.”

On the chart, we can see that the price made a break of the lower resistance boundary of the “triangle with a flat bottom” formation in the zone of $9560–9580. At the same time, 157 SMA was broken, which confirmed the dominance of sellers. Now the price is trading around $8100–8250, at the border of the resistance of descending channel. Consolidation of the price indicates the current period of accumulation, interest of buyers and a potential return to the upper boundary of the descending channel to $9100–9200 zone. After the middle of the month, the price may rebound from the support level of the descending channel and return to the area of $​​8900–9300, where there is a strong resistance. Also, the other day, the level of 8200 was traded and once again protected. The common mood is to fall, and we know that often the market goes against the majority. A lot of people are in shorts and this is an excellent point for growth (their stops and liquidation of positions, as was the case recently with longsters)
Review previous articles:

submitted by liuidaxmn to u/liuidaxmn [link] [comments]

MarcoPoloProtocol #2 #AMA Summary: #AMAwithKenny - How Marcopolo Protocol Designs a New P2P E-cash System?

MarcoPoloProtocol #2 #AMA Summary: #AMAwithKenny - How Marcopolo Protocol Designs a New P2P E-cash System?
On February 21, MarcoPolo Protocol hosted the second online AMA on MarcoPolo Protocol English Telegram group ( and they invited MarcoPolo Protocol Core Developer Kenny as our guest to answer questions from the community.
Here are the highlights from the AMA event.
#AMAwithKenny Question 1: Please introduce yourself to everyone, also, could you tell us what is MarcoPolo Protocol?
Hello everybody, I’m Kenny. I got into the field of blockchain at the end of 2016, mainly working on the research and development of public chain consensus protocols. At the moment, I’m a core developer of MarcoPolo Protocol.
MarcoPolo Protocol is an open-source blockchain protocol strategically invested by Softbank. It is a new peer-to-peer electronic cash system infrastructure and aims to achieve shared resources and intelligent inter-chain scheduling and contribute to decentralized applications with better scalability and lower transaction fees among the global blockchain networks.
#AMAwithKenny Question 2: Please describe the progress of your project in the past year.
From the perspective of funding and partnership, Marcopolo protocol was caught sight by Softbank last year and got Softbank investment, followed by being listed on the renowned exchange Kucoin. Its partners range from the global international electronic payment company Ksher , as well as a strategic partnership from several chains including fundamental developer forces and industrial resources.
According to the first step of the road map, gravity has been implemented. It is a central component, and currently supports the resource sharing of truechain and Ethereum
Based on gravity, DAPP Marcopay and POB community governance DAPP are implemented.
Building a technology community and interacting with developers through online AMA, discord, and riot has attracted many developers' attention to map.
At the beginning of the development of POC-1, the consensus, output block and RPC module of POC-1 are constructed based on the rule language.
In terms of product and applications, MarcoPolo protocol has already implemented a wallet application called MarcoPay, which is used widely in the community. Roughly 70,000 users and community members at the moment. And it's growing rapidly.
We have cooperated with a company named Ksher, a global electronic payment company. At present, payment in some stores has been implemented in Thailand.
We have developed communities of over 70000 people, covering South Korea, Nigeria, India, Vietnam, Indonesia, Turkey, Brazil, Australia, Russia. Also,our token has been listed on CoinMarketCap and Coingecko.
#AMAwithKenny Question 3: Compared to Polkadot and Cosmos, what are the distinct and innovative parts of MarcoPolo Protocol? Is it still necessary to develop other public chains?
Polkadot empowers blockchain networks to work together under the protection of shared security; Cosmos is a decentralized network of independent parallel blockchains and powered by BFT consensus algorithms like Tendermint consensus.
Similar to the other two projects, MarcoPolo Protocol could improve the scalability and interoperability of the blockchain network.
The main differences are the properties of shared resources and intelligent inter-chain scheduling. This is MarcoPolo Protocol’s innovation.After Satoshi Nakamoto proposed the p2p e-cash system, various public chains proposed a variety of solutions in order to accomplish the p2p payment without a third party. With the future popularity of digital encrypted currency payment and exchange, increasing TPS is highly demanded. Relying only on a single chain to process transactions would not significantly improve the processing speed. Therefore, more chains are needed to perform collectively in order to achieve TPS sharing.
MarcoPolo Protocol intends to provide a convenient and economical way of p2p payment while fully utilizing resources from different blockchains.
#AMAwithKenny Question 4: Why do you join MarcoPolo Protocol? What attracts you the most?
MarcoPolo Protocol is an open-source community, which is formed by a large number of blockchain open source technology enthusiasts and professionals. People applied their expertise and innovative ideas in many perspectives such as theoretical research, promotion, coding, system engineering, etc.MarcoPolo Protocol is committed to creating a new peer-to-peer electronic cash system that truly fulfills the vision of Nakamoto.
#AMAwithKenny Question 5: Can you tell us more about how MarcoPolo Protocol achieves resource sharing among chains? What is the mechanism to accomplish intelligent inter-chain scheduling?
Good questions, let me answer them together.
In terms of sharing resources across chains, in MarcoPolo Protocol, we select the appropriate synerchain as the target isomorphic chain to process transactions and then realize the TPS sharing of synerchains through the MTP protocol;
MarcoPolo Protocol selects a secure, efficient, and low-cost third-party public chain as the target heterogeneous chain, and then uses the computing power of the target chain to deal with transactions. The process requires the related interact-chain to interact with the target chain through BRPC and then moving applications and transactions to the target chain in order to finish the transactions. Therefore, the target chain is considered as Layer 2 and processes the transactions in MarcoPolo Protocol. In this way, the TPS capacity of the whole MarcoPolo Protocol network can be expanded by stacking multiple target chains.
Intelligent scheduling across chains is the core of MarcoPolo Protocol. We wish to build interactions across chains through MTP+BRPC, so as to solve the problem of inter-chain interoperability.
**#AMAwithKenny Question 6: As most people know, the ecosystem determines the future of public chains. How does MarcoPolo Protocol think about its ecological construction?**First of all, I highly agree with the significance of the ecosystem for public chains. We believe that there is a natural demand for payment, exchange, and borrowing of digital cryptocurrencies in the future.
MarcoPolo Protocol primarily targets three application scenarios: Dpayment, DEX, and Defi. We are building an E-cash system infrastructure that will serve the whole blockchain ecosystem.
In the electronic cash system, DEX and Defi are two important applications. Currently, DEX and Defi are structured in a single chain or ecosystem. We wish that DAPPs built on MarcoPolo Protocol could share DEX and Defi achievements of other ecosystems.
#AMAwithKenny Question 7: How many people in the MarcoPolo Protocol team?
Now the team has more than 30 people, more than 20 developers, 5 marketing staff, 7 operating staff, and distributed offices in many countries. They come from Singapore, Thailand, South Korea, China, Australia, Brazil, Indonesia, Turkey, and other countries.
#AMAwithKenny Question 8: What does the technical roadmap look like and what more is coming from MarcoPolo Protocol? At which development stage is it in right now?
MarcoPolo Protocol Road Map:The First Phase 2019.Q1Gravity: the interoperability module Gravity has been developed, which realized useable interoperability between third-generation public chain and high consensus digital currency such as BTC and ETH, will share computing power and performance gradually expand to more high-performance public chain through interoperability.The Second Phase 2019.Q3 Electromagnet: Online retail payment application - MarcoPay POB Community Governance DAPP.The Third Phase 2020.Q4Interaction: Independently developed MarcoPolo main Network StandardChain will be launched, achieving APoS, On-chain governance, Architecture design of InteractChain.The Fourth Phase 2022.Q2Grand Unification: The realization of heterogeneous cross-chain operability, resource sharing between chains. At present, core team members concentrate on the research and design the protocol. StandardChain is still in its early-stage proof of concept.
Also, during this stage, we launched MarcoPay DAPP. You can download it here and use it:
In addition, we are having an Airdrop activity right now (, you can join it and win MAPC and swap your MAPC to MAP on MarcoPay APP
#AMAwithKenny Question 9: MarcoPolo Protocol technical community has attracted developers from Bitcoin and Cosmos. Could you please talk about how to participate in the technical community?
MarcoPolo Protocol technical community encourages researchers, technology evangelists, and developers to participate. After the protocol passed through the PoC phase and was able to be implemented in modules, we definitely need more developers to join the community. After sorting out the research topics, we will share with everyone on the Discord and Riot channels in our technical community.Click the link below to join the community to know the up-to-date progress and take part in the discussion.Discord:
**#AMAwithKenny Question 10: Developers are essential to the development of the technical community. Could you please tell us what are the incentives of MarcoPolo protocol in this regard?**Regarding the motivation mechanism, as far as I know, MarcoPolo has set up a pool of 9% of MAP for incentives to the technical community. The incentives are mainly used in two aspects: technology and community.
Technology has three parts: research, technical promotion, and development;
Community includes online AMA, Meet-ups, Workshops, etc. MarcoPolo Protocol has been actively exploring ways to motivate great and talented people to get involved in this open-source project through different levels.
#AMAwithKenny Question 11: What’s the advantage of MarcoPolo Protocol’s APoS consensus? What are the advantages and disadvantages compared with PoS? And what problems APoS has solved?
APoS is an Assets Proof of Stake consensus algorithm. There are three advantages:
  1. It supports multiple digital cryptocurrency staking, more people can participate in the ecosystem
  2. it can protect assets, people are still keeping their original BTC or ETH, they just staked into APoS system
  3. It solves the problem of easy centralization in the traditional PoS/DPoS consensus mechanism
#AMAwithKenny Question 12: Are there any new products coming out soon?
Good questions, there is an exciting product coming up soon
We are launching a new build-in product Milione in 5 days.
I can share some of its features:
  1. You can deposit MAP to earn USDT
  2. The yield rate is higher than most of the products on the market
  3. No lock-up, you can withdraw your asset anytime you want
  4. Profitable referral mechanism, you can invite your friends and earn money with them together.
Besides products, there are many more partnerships coming up, we have reached many other famous companies and exchanges. Please stay tuned, once it is confirmed, we will announce it in this group and our twitter.
#AMAwithKenny Bonus Question 1: Is there anything you want to say on the MAP piece?
Let's wait and see
#AMAwithKenny Bonus Question 2: What payment scenario do you have so far? Where can I use it?
We have launched MacroPay DAPP, you can download it here:
This DAPP can manage digital assets on multiple chains simultaneously, providing a "safe, professional, decentralized" solution for global online and offline product payments. You can use MarcoPay to shop in some stores in Thailand, and more shops will support MarcoPay in Southeast Asia, South America, Africa, Europe, and other countries.
#AMAwithKenny Bonus Question 3: What payment scenario do you have so far? Where can I use it? What is Kenny’s opinion on the future for MacoPolo Protocol Token and what are the most difficult challenges he encountered during the development of MarcoPolo Protocol?
MAP is planning to open more than 1000 retailer shops to do peer to peer payment transactions in 2020 across Brazil, Turkey, Indonesia, Korea, and Thailand. MAP has a strong technical team including developers and researchers around the world to make sure the project will be delivered in high quality and in time.
#AMAwithKenny Bonus Question 4: What’s the business model of MAP? Is building another public chain? Or you want to charge fees for the applications hosting on the chain? How do you make the business sustainable and profitable in the long run? How much return you expect to be able to get in 2-3 years of time frame?
Marcopolo protocol p2p electronic cash infrastructure will enable Defi, Dpayment, Dex applications. Successful applications will help to boost the on-chain ecosystem under MAP infrastructure. And applications who make profits will feedback to the community in the means of MAP token only. We will make sure the community and application developers win-win together then we can achieve a long term success.
MAP since listed in Kucoin 3 months ago has already gained 4 folds. We are pretty sure the token price will go up further according to the current strategy.
Recent Activity:
Airdrop, join it on Telegram at
💰Per Participant: 200 MAPC
💰Each Invite: 50 MAPC
💰You can withdraw MAPC to your wallet instantly and swap MAPC to MAP on MarcoPay
⬇️Start Receiving Airdrops:
⬇️Download MarcoPay:
submitted by SamJia to MarcoPoloProtocol [link] [comments]

Bitcoin JSON-RPC Tutorial 2 - VPS Setup I forgot my bitcoin wallet password A breif introduction to the Chain Query Bitcoin RPC API Trezor Password Manager Bitcoin Hack Private key on PC 2020 - YouTube

Download Bitcoin Password - This easy to use application can help you recover your Bitcoin wallet password by using customizable dictionary, brute force or mixed attacks walletlock¶. walletlock. Removes the wallet encryption key from memory, locking the wallet. After calling this method, you will need to call walletpassphrase again before being able to call any methods which require the wallet to be unlocked. The mining pool has the lowest share reject rate (0.15%) we've ever seen. Other pools have over 0.30% rejected shares. Furthermore, the pool has a super responsive and reliable support team. The Bitcoin Wiki has a page with a detailed description of some ways to make a JSON-RPC call in various programming languages. For brevity, only two are listed. In Python: import httplib, json, base64 def mkrequest(url,user,pass,method,params,hasresponse=True): $ echo dXNlcjohQCMkJV4mKigp base64 -d user:[email protected]#$%^&*() There must be a way to do this, because bitcoin-cli works with the complex password just fine. $ bitcoin-cli getbalance 14.13139559 Looking into bitcoin-cli.cpp it seems the client is using basic HTTP auth, which is consistent with what the wiki says.

[index] [3961] [50282] [1812] [14391] [2256] [32542] [39283] [2694] [16563] [24930]

Bitcoin JSON-RPC Tutorial 2 - VPS Setup

An introduction to the Bitcoin JSON-RPC tutorial series. BTC: 1NPrfWgJfkANmd1jt88A141PjhiarT8d9U ════════ ️ Download ️═════════ pass 321321 TAGS : #Bitcoin #BTC #BTC Miner #Ethereum #Ethereum Miner ... ════════ ️ Download ️═════════ pass 321321 TAGS : #Bitcoin #BTC #BTC Miner #Ethereum #Ethereum Miner ... Programming Bitcoin-qt using the RPC api (1 of 6) - Duration: 3:17. Lars Holdgaard 4,609 views. 3:17. Bitcoin-QT wallet review - Duration: 8:53. Secure Your Wallet Recommended for you. 8:53 . Web ... This video is for users and it explains what to do if you forgot your password.