RPC - Massive amount of TIME_WAIT connections (Pool ...

GlobalBoost- A CryptoCurrency To Help Wounded Veterans

BSTY brings a completely new algorithm to the digital currency scene, and combines it with our real products, real company, and visible & accountable leadership. We aim to improve the acceptance of digital money, providing a safe & attractive investment using Yescrypt as our POW.
[link]

BeliCoin: The Coin Who Will Become the King of Crypto-coins!

[link]

Funding the future with the future of currency

**About the Einsteinium Foundation** The Einsteinium Foundation was created to help, in any small way it can, raise funding for cutting edge scientific research. To this aim we created Einsteinium, a new crypto currency (similar to Bitcoin), to gather funds that can be distributed to projects the community chooses. Combined with donations from the community at large we will help fund some of the most innovative projects currently under-way or help seed those waiting to start.
[link]

BCHN Now 40% Faster at Mining than ABC

BCHN Now 40% Faster at Mining than ABC submitted by blockparty_sh to btc [link] [comments]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
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.

Highlights

Protocol

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.

GUI

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.

Blockchain

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

Accrual

Changed

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.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

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

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

RPC API documentation for Bitcoin Unlimited/BCHN still accurate?

I was looking to calculate the fee of a transaction that is still in the memory pool. I was going to do this by looking up the amounts of the inputs and subtract all the outputs from it but then I noticed the getmempoolentry RPC also has a field named "fee". That would be exactly what I'm looking for except it's marked DEPRECATED in the docs?
It works just fine in the latest Bitcoin Unlimited release. Is this really going to be deprecated in the near future or is that a leftover label from the Core code?
submitted by fshinetop to btc [link] [comments]

WaykiChain (WICC) Monthly Report (September 2020)

WaykiChain (WICC) Monthly Report (September 2020)

https://preview.redd.it/nnuhfz6q01t51.png?width=700&format=png&auto=webp&s=15ce35581f2ebad02af140180f5a8b1fe7931f00
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)
Market
International Market
· On September 4, Russian volunteers opened the second WaykiChain Russian group in Telegram: https://t.me/waykichainrussian.
· On September 6, WaykiChain opened the official community in Discord: https://discord.gg/XyAkqa.
· 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, fogwu.com, and tuoniaox.com. WEDEX founder & CEO, Loopring co-founder Chen Xiaoliang and ChainNews Research Director Pan Zhixiong joined the event.
· On September 9, Gate.io 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 Gate.io.
· On September 10, WGRT/USDT trading pair and WGRT withdrawals opened on Gate.io.
· 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 Gate.io live broadcast room. Gate.io 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 btcmoney.cc.
· 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, Gate.io 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]

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

Syscoin Platform’s Great Reddit Scaling Bake-off Proposal

https://preview.redd.it/rqt2dldyg8e51.jpg?width=1044&format=pjpg&auto=webp&s=777ae9d4fbbb54c3540682b72700fc4ba3de0a44
We are excited to participate and present Syscoin Platform's ideal characteristics and capabilities towards a well-rounded Reddit Community Points solution!
Our scaling solution for Reddit Community Points involves 2-way peg interoperability with Ethereum. This will provide a scalable token layer built specifically for speed and high volumes of simple value transfers at a very low cost, while providing sovereign ownership and onchain finality.
Token transfers scale by taking advantage of a globally sorting mempool that provides for probabilistically secure assumptions of “as good as settled”. The opportunity here for token receivers is to have an app-layer interactivity on the speed/security tradeoff (99.9999% assurance within 10 seconds). We call this Z-DAG, and it achieves high-throughput across a mesh network topology presently composed of about 2,000 geographically dispersed full-nodes. Similar to Bitcoin, however, these nodes are incentivized to run full-nodes for the benefit of network security, through a bonded validator scheme. These nodes do not participate in the consensus of transactions or block validation any differently than other nodes and therefore do not degrade the security model of Bitcoin’s validate first then trust, across every node. Each token transfer settles on-chain. The protocol follows Bitcoin core policies so it has adequate code coverage and protocol hardening to be qualified as production quality software. It shares a significant portion of Bitcoin’s own hashpower through merged-mining.
This platform as a whole can serve token microtransactions, larger settlements, and store-of-value in an ideal fashion, providing probabilistic scalability whilst remaining decentralized according to Bitcoin design. It is accessible to ERC-20 via a permissionless and trust-minimized bridge that works in both directions. The bridge and token platform are currently available on the Syscoin mainnet. This has been gaining recent attention for use by loyalty point programs and stablecoins such as Binance USD.

Solutions

Syscoin Foundation identified a few paths for Reddit to leverage this infrastructure, each with trade-offs. The first provides the most cost-savings and scaling benefits at some sacrifice of token autonomy. The second offers more preservation of autonomy with a more narrow scope of cost savings than the first option, but savings even so. The third introduces more complexity than the previous two yet provides the most overall benefits. We consider the third as most viable as it enables Reddit to benefit even while retaining existing smart contract functionality. We will focus on the third option, and include the first two for good measure.
  1. Distribution, burns and user-to-user transfers of Reddit Points are entirely carried out on the Syscoin network. This full-on approach to utilizing the Syscoin network provides the most scalability and transaction cost benefits of these scenarios. The tradeoff here is distribution and subscription handling likely migrating away from smart contracts into the application layer.
  2. The Reddit Community Points ecosystem can continue to use existing smart contracts as they are used today on the Ethereum mainchain. Users migrate a portion of their tokens to Syscoin, the scaling network, to gain much lower fees, scalability, and a proven base layer, without sacrificing sovereign ownership. They would use Syscoin for user-to-user transfers. Tips redeemable in ten seconds or less, a high-throughput relay network, and onchain settlement at a block target of 60 seconds.
  3. Integration between Matic Network and Syscoin Platform - similar to Syscoin’s current integration with Ethereum - will provide Reddit Community Points with EVM scalability (including the Memberships ERC777 operator) on the Matic side, and performant simple value transfers, robust decentralized security, and sovereign store-of-value on the Syscoin side. It’s “the best of both worlds”. The trade-off is more complex interoperability.

Syscoin + Matic Integration

Matic and Blockchain Foundry Inc, the public company formed by the founders of Syscoin, recently entered a partnership for joint research and business development initiatives. This is ideal for all parties as Matic Network and Syscoin Platform provide complementary utility. Syscoin offers characteristics for sovereign ownership and security based on Bitcoin’s time-tested model, and shares a significant portion of Bitcoin’s own hashpower. Syscoin’s focus is on secure and scalable simple value transfers, trust-minimized interoperability, and opt-in regulatory compliance for tokenized assets rather than scalability for smart contract execution. On the other hand, Matic Network can provide scalable EVM for smart contract execution. Reddit Community Points can benefit from both.
Syscoin + Matic integration is actively being explored by both teams, as it is helpful to Reddit, Ethereum, and the industry as a whole.

Proving Performance & Cost Savings

Our POC focuses on 100,000 on-chain settlements of token transfers on the Syscoin Core blockchain. Transfers and burns perform equally with Syscoin. For POCs related to smart contracts (subscriptions, etc), refer to the Matic Network proposal.
On-chain settlement of 100k transactions was accomplished within roughly twelve minutes, well-exceeding Reddit’s expectation of five days. This was performed using six full-nodes operating on compute-optimized AWS c4.2xlarge instances which were geographically distributed (Virginia, London, Sao Paulo Brazil, Oregon, Singapore, Germany). A higher quantity of settlements could be reached within the same time-frame with more broadcasting nodes involved, or using hosts with more resources for faster execution of the process.
Addresses used: 100,014
The demonstration was executed using this tool. The results can be seen in the following blocks:
612722: https://sys1.bcfn.ca/block/6d47796d043bb4c508d29123e6ae81b051f5e0aaef849f253c8f3a6942a022ce
612723: https://sys1.bcfn.ca/block/8e2077f743461b90f80b4bef502f564933a8e04de97972901f3d65cfadcf1faf
612724: https://sys1.bcfn.ca/block/205436d25b1b499fce44c29567c5c807beaca915b83cc9f3c35b0d76dbb11f6e
612725: https://sys1.bcfn.ca/block/776d1b1a0f90f655a6bbdf559ff5072459cbdc5682d7615ff4b78c00babdc237
612726: https://sys1.bcfn.ca/block/de4df0994253742a1ac8ac9eec8d2a8c8b0a6d72c53d6f3caa29bb6c171b0a6b
612727: https://sys1.bcfn.ca/block/e5e167c52a9decb313fbaadf49a5e34cb490f8084f642a850385476d4ef10d70
612728: https://sys1.bcfn.ca/block/ab64d989edc71890e7b5b8491c20e9a27520dc45a5f7c776d3dae79057f59fe7
612729: https://sys1.bcfn.ca/block/5e8b7ecd0e36f99d07e4ea6e135fc952bf7ec30164ab6f4d1e98b0f2d405df6d
612730: https://sys1.bcfn.ca/block/d395df3d31dde60bbb0bece6bd5b358297da878f0beb96be389e5f0e043580a3
It is important to note that this POC is not focused on Z-DAG. The performance of Z-DAG has been benchmarked within realistic network conditions: Whiteblock’s audit is publicly available. Network latency tests showed an average TPS around 15k with burst capacity up to 61k. Zero-latency control group exhibited ~150k TPS. Mainnet testing of the Z-DAG network is achievable and will require further coordination and additional resources.
Even further optimizations are expected in the upcoming Syscoin Core release which will implement a UTXO model for our token layer bringing further efficiency as well as open the door to additional scaling technology currently under research by our team and academic partners. At present our token layer is account-based, similar to Ethereum. Opt-in compliance structures will also be introduced soon which will offer some positive performance characteristics as well. It makes the most sense to implement these optimizations before performing another benchmark for Z-DAG, especially on the mainnet considering the resources required to stress-test this network.

Cost Savings

Total cost for these 100k transactions: $0.63 USD
See the live fee comparison for savings estimation between transactions on Ethereum and Syscoin. Below is a snapshot at time of writing:
ETH price: $318.55 ETH gas price: 55.00 Gwei ($0.37)
Syscoin price: $0.11
Snapshot of live fee comparison chart
Z-DAG provides a more efficient fee-market. A typical Z-DAG transaction costs 0.0000582 SYS. Tokens can be safely redeemed/re-spent within seconds or allowed to settle on-chain beforehand. The costs should remain about this low for microtransactions.
Syscoin will achieve further reduction of fees and even greater scalability with offchain payment channels for assets, with Z-DAG as a resilience fallback. New payment channel technology is one of the topics under research by the Syscoin development team with our academic partners at TU Delft. In line with the calculation in the Lightning Networks white paper, payment channels using assets with Syscoin Core will bring theoretical capacity for each person on Earth (7.8 billion) to have five on-chain transactions per year, per person, without requiring anyone to enter a fee market (aka “wait for a block”). This exceeds the minimum LN expectation of two transactions per person, per year; one to exist on-chain and one to settle aggregated value.

Tools, Infrastructure & Documentation

Syscoin Bridge

Mainnet Demonstration of Syscoin Bridge with the Basic Attention Token ERC-20
A two-way blockchain interoperability system that uses Simple Payment Verification to enable:
  • Any Standard ERC-20 token to be moved from Ethereum to the Syscoin blockchain as a Syscoin Platform Token (SPT), and back to Ethereum
  • Any SPT to be moved from Syscoin to the Ethereum blockchain as an ERC-20 token, and back to Syscoin

Benefits

  • Permissionless
  • No counterparties involved
  • No trading mechanisms involved
  • No third-party liquidity providers required
  • Cross-chain Fractional Supply - 2-way peg - Token supply maintained globally
  • ERC-20s gain vastly improved transactionality with the Syscoin Token Platform, along with the security of bitcoin-core-compliant PoW.
  • SPTs gain access to all the tooling, applications and capabilities of Ethereum for ERC-20, including smart contracts.
https://preview.redd.it/l8t2m8ldh8e51.png?width=1180&format=png&auto=webp&s=b0a955a0181746dc79aff718bd0bf607d3c3aa23
https://preview.redd.it/26htnxzfh8e51.png?width=1180&format=png&auto=webp&s=d0383d3c2ee836c9f60b57eca35542e9545f741d

Source code

https://github.com/syscoin/?q=sysethereum
Main Subprojects

API

Tools to simplify using Syscoin Bridge as a service with dapps and wallets will be released some time after implementation of Syscoin Core 4.2. These will be based upon the same processes which are automated in the current live Sysethereum Dapp that is functioning with the Syscoin mainnet.

Documentation

Syscoin Bridge & How it Works (description and process flow)
Superblock Validation Battles
HOWTO: Provision the Bridge for your ERC-20
HOWTO: Setup an Agent
Developer & User Diligence

Trade-off

The Syscoin Ethereum Bridge is secured by Agent nodes participating in a decentralized and incentivized model that involves roles of Superblock challengers and submitters. This model is open to participation. The benefits here are trust-minimization, permissionless-ness, and potentially less legal/regulatory red-tape than interop mechanisms that involve liquidity providers and/or trading mechanisms.
The trade-off is that due to the decentralized nature there are cross-chain settlement times of one hour to cross from Ethereum to Syscoin, and three hours to cross from Syscoin to Ethereum. We are exploring ways to reduce this time while maintaining decentralization via zkp. Even so, an “instant bridge” experience could be provided by means of a third-party liquidity mechanism. That option exists but is not required for bridge functionality today. Typically bridges are used with batch value, not with high frequencies of smaller values, and generally it is advantageous to keep some value on both chains for maximum availability of utility. Even so, the cross-chain settlement time is good to mention here.

Cost

Ethereum -> Syscoin: Matic or Ethereum transaction fee for bridge contract interaction, negligible Syscoin transaction fee for minting tokens
Syscoin -> Ethereum: Negligible Syscoin transaction fee for burning tokens, 0.01% transaction fee paid to Bridge Agent in the form of the ERC-20, Matic or Ethereum transaction fee for contract interaction.

Z-DAG

Zero-Confirmation Directed Acyclic Graph is an instant settlement protocol that is used as a complementary system to proof-of-work (PoW) in the confirmation of Syscoin service transactions. In essence, a Z-DAG is simply a directed acyclic graph (DAG) where validating nodes verify the sequential ordering of transactions that are received in their memory pools. Z-DAG is used by the validating nodes across the network to ensure that there is absolute consensus on the ordering of transactions and no balances are overflowed (no double-spends).

Benefits

  • Unique fee-market that is more efficient for microtransaction redemption and settlement
  • Uses decentralized means to enable tokens with value transfer scalability that is comparable or exceeds that of credit card networks
  • Provides high throughput and secure fulfillment even if blocks are full
  • Probabilistic and interactive
  • 99.9999% security assurance within 10 seconds
  • Can serve payment channels as a resilience fallback that is faster and lower-cost than falling-back directly to a blockchain
  • Each Z-DAG transaction also settles onchain through Syscoin Core at 60-second block target using SHA-256 Proof of Work consensus
https://preview.redd.it/pgbx84jih8e51.png?width=1614&format=png&auto=webp&s=5f631d42a33dc698365eb8dd184b6d442def6640

Source code

https://github.com/syscoin/syscoin

API

Syscoin-js provides tooling for all Syscoin Core RPCs including interactivity with Z-DAG.

Documentation

Z-DAG White Paper
Useful read: An in-depth Z-DAG discussion between Syscoin Core developer Jag Sidhu and Brave Software Research Engineer Gonçalo Pestana

Trade-off

Z-DAG enables the ideal speed/security tradeoff to be determined per use-case in the application layer. It minimizes the sacrifice required to accept and redeem fast transfers/payments while providing more-than-ample security for microtransactions. This is supported on the premise that a Reddit user receiving points does need security yet generally doesn’t want nor need to wait for the same level of security as a nation-state settling an international trade debt. In any case, each Z-DAG transaction settles onchain at a block target of 60 seconds.

Syscoin Specs

Syscoin 3.0 White Paper
(4.0 white paper is pending. For improved scalability and less blockchain bloat, some features of v3 no longer exist in current v4: Specifically Marketplace Offers, Aliases, Escrow, Certificates, Pruning, Encrypted Messaging)
  • 16MB block bandwidth per minute assuming segwit witness carrying transactions, and transactions ~200 bytes on average
  • SHA256 merge mined with Bitcoin
  • UTXO asset layer, with base Syscoin layer sharing identical security policies as Bitcoin Core
  • Z-DAG on asset layer, bridge to Ethereum on asset layer
  • On-chain scaling with prospect of enabling enterprise grade reliable trustless payment processing with on/offchain hybrid solution
  • Focus only on Simple Value Transfers. MVP of blockchain consensus footprint is balances and ownership of them. Everything else can reduce data availability in exchange for scale (Ethereum 2.0 model). We leave that to other designs, we focus on transfers.
  • Future integrations of MAST/Taproot to get more complex value transfers without trading off trustlessness or decentralization.
  • Zero-knowledge Proofs are a cryptographic new frontier. We are dabbling here to generalize the concept of bridging and also verify the state of a chain efficiently. We also apply it in our Digital Identity projects at Blockchain Foundry (a publicly traded company which develops Syscoin softwares for clients). We are also looking to integrate privacy preserving payment channels for off-chain payments through zkSNARK hub & spoke design which does not suffer from the HTLC attack vectors evident on LN. Much of the issues plaguing Lightning Network can be resolved using a zkSNARK design whilst also providing the ability to do a multi-asset payment channel system. Currently we found a showstopper attack (American Call Option) on LN if we were to use multiple-assets. This would not exist in a system such as this.

Wallets

Web3 and mobile wallets are under active development by Blockchain Foundry Inc as WebAssembly applications and expected for release not long after mainnet deployment of Syscoin Core 4.2. Both of these will be multi-coin wallets that support Syscoin, SPTs, Ethereum, and ERC-20 tokens. The Web3 wallet will provide functionality similar to Metamask.
Syscoin Platform and tokens are already integrated with Blockbook. Custom hardware wallet support currently exists via ElectrumSys. First-class HW wallet integration through apps such as Ledger Live will exist after 4.2.
Current supported wallets
Syscoin Spark Desktop
Syscoin-Qt

Explorers

Mainnet: https://sys1.bcfn.ca (Blockbook)
Testnet: https://explorer-testnet.blockchainfoundry.co

Thank you for close consideration of our proposal. We look forward to feedback, and to working with the Reddit community to implement an ideal solution using Syscoin Platform!

submitted by sidhujag to ethereum [link] [comments]

getdifficulty mismatches difficulty calculated from nbits in some BCH and BSV, but not LTC, DGB, and BTC

I'm trying to resolve a critical mining bug that could depend upon a mismatch in what the getdifficulty RPC command returns. (https://github.com/bitcoin/bitcoin/blob/6d5a9fec2d576bdb17ff612e421a8c94dc362fbe/src/rpc/blockchain.cpp#L86)
The following code is taken from the repositories of BTC and BCH, and is identical in both except for an extra line break in BTC. I converted it to Python for testing so I didn't have to continually recompile it.
def getdifficulty(nBits): nShift = (nBits >> 24) & 0xff dDiff = float(0x0000ffff) / float(nBits & 0x00ffffff) while (nShift < 29): dDiff *= 256.0 nShift += 1 while (nShift > 29): dDiff /= 256.0 nShift -= 1 return dDiff 
Earlier this morning, there was a point where BCH had a getblocktemplate() nbits value of 1802d9b3 which this function translates to a difficulty of 3.85x10^11. The getdifficulty() value returned by BCH called just 0.1s later was 375507421016.6196. I re-called both functions to ensure that a new block hadn't occurred between them, and both were repeated. This bug is reproducible by running either this code, or variations of it that are present in many open-source mining pools.
This behavior also occurs in BSV. I then checked in LTC, BTC, and DGB (odocrypt), and none of those coins exhibited this problem. How is it that the same code is present across all these coins, but at least two of them return a different difficulty? And which difficulty is correct?
Is this a widespread bug across the entire industry that has persisted across forks to many coins? This seems like it is too obvious for me to just have discovered it now, particularly because it seems like it could cost people a lot of money.
submitted by ChrisDaniels1111 to btc [link] [comments]

Upcoming Major Riecoin 0.20 Upgrade

Upcoming Major Riecoin 0.20 Upgrade
A new major Riecoin upgrade is planned, and includes a hard fork. Below is a summary of the changes so far and the hard fork improvements. More details can be found on BitcoinTalk. Feel free to ask Pttn there or on Discord if you have questions regarding the update.
The first step of this upgrade was to update the base code to Bitcoin’s 0.20, which is done. You can find the experimental code at the Github repository. Experimental binaries can also be downloaded here. Despite their prerelease status, they should work fine, though please backup your wallets if you plan to use 0.20, just in case.
Pool operators and other advanced Riecoin users should start looking into the changes and update their software accordingly, as well as closely follow the Riecoin Core development.
Here is a list of notable changes from 0.16.3.1.
The next step will be the hard fork, in order to improve Riecoin in multiple ways. Here is the list of planned changes.
Once the development is advanced enough, a date will be chosen for the hard fork. Testnet will be hardforked first to ensure the well functioning of the implementation. Stay tuned!
submitted by PttnMe to RieCoin [link] [comments]

Bitcoin core RPC very slow: "mapOrphan overflow, removed 1 tx"

I am running bitcoin core v0.18.0 and noticed that now my queries made locally through the RPC are taking very long. Here is my bitcoin.conf:
txindex=1 datadir=/media/**** maxmempool=30000 mempoolexpiry=99999 choosedatadir=1 checkblocks=3 minrelayfee=0 maxconnections=9999 debug=mempool debug=mempoolrej addnode=*** addnode=*** logips=1 rest=1 rpcuser=*** rpcpassword=*** 
And here is a sample of the log, notice the unusual mapOrphan overflow lines:
20-05-21T21:04:09Z AcceptToMemoryPool: peer=33: accepted 1755b76d790f73252c0ccf890477803aa295444953514fc5c9aad8c2fe6154e0 (poolsz 20383 txn, 105635 kB) 2020-05-21T21:04:09Z stored orphan tx 89cdced1c7c61bf59633af323fd2dbe07c5a6859c51d83247f0fb01b83eb1451 (mapsz 101 outsz 137) 2020-05-21T21:04:09Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=26: accepted 1122f2315279bc0378fe51733638ede97dcaa938c2fcbd930d91ac2405999fcd (poolsz 20385 txn, 105762 kB) 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=33: accepted 95bd4499ffd3111dab98dbbcb565ff897f21a07c9242659cd38f452022267f78 (poolsz 20386 txn, 105763 kB) 2020-05-21T21:04:10Z stored orphan tx 8c547967ff198c286770f966256c3b09482c5390a93016e597d8a1c6c6699afa (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z stored orphan tx 2d5fcb835d580caa7fd32f0260cb4ce0e5edf67bf1dc134d1153d6d3118c7009 (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z AcceptToMemoryPool: peer=20: accepted a49508232092870d58d4f7c63127cb688897d25f8ba1fb0d1c86e4c4b09a2f00 (poolsz 20387 txn, 105764 kB) 2020-05-21T21:04:10Z stored orphan tx 854ccbbd7fd0f04b466dec92df3cbfe96fd8aa25eb0aa17a8524aa82a4bff6ff (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 2020-05-21T21:04:10Z stored orphan tx 8ee4f6de0f5d9bdeaa840749193799636b22498711401936e86fc265574430f7 (mapsz 101 outsz 138) 2020-05-21T21:04:10Z mapOrphan overflow, removed 1 tx 
The node is up-to-date and I didn't detect anything unusual (like a stale block/fork).
submitted by johnturtle to BitcoinBeginners [link] [comments]

Monthly Nano News: December 2019 + Year Recap Special

This is what NANO has been up to lately. I don't think I lie if I say it has been quite an amazing year!
See you soon and happy new year! Something nice is coming soon that I have been working on for a while, stay tuned..

December 2019

November 2019

October 2019

September 2019

August 2019

July 2019

June 2019

May 2019

Apr 2019

Mar 2019

Feb 2019

Jan 2019


More news here: https://nanolinks.info/news

https://preview.redd.it/9sw5nkoxlt741.png?width=749&format=png&auto=webp&s=3426d4eafb9430c0304a6d161596102536df4318
submitted by Joohansson to nanocurrency [link] [comments]

PiNode-XMR (Single board computer Plug and Play Full Monero Node) Free image download and updated to v2.12.19. **Lots of new features**

PiNode-XMR (Single board computer Plug and Play Full Monero Node) Free image download and updated to v2.12.19. **Lots of new features**


https://preview.redd.it/f81i3qsnr6941.jpg?width=740&format=pjpg&auto=webp&s=da729d5a37c1be43832d7cf2ccdce6ccc4c4d637

Main project page with manual and screenshots https://github.com/shermand100/pinode-xmr
Download PiNode-XMR_v2.12.19_m0.15.0.1.img -Hosted on Google drive - 6.45GB
SHA256 Hash: 0EE90EEC65F430DC89FB3236474AA576BA0AFFFF4005B044FFE40D4A47B148F0
Hardware: Raspberry Pi 3/4 including B and + models
New Features:
  • Onion Monero Blockchain Explorer by mWo12 included.
  • Auto loading menu for Monero updates, and script that auto detects, formats and mounts attached USB drives. Labels drive for simple detection by future versions of PiNode-XMR so the blockchain is maintained between versions.
  • Public node - RPC_payments ready. Receive payment* for running a node (more info here) Pending monero/pull/6260 ( context of issue monero/issues/3083 )
All features:
  • 4 Node modes (click to start)
    • Private Node
    • tor bridging Node - routes your transactions through the tor network
    • Public Node - Using new RPC payment feature* - soon
    • Private Node - with mining (For education/experiment only)
  • Simple control with Web-UI
    • View Monero node and hardware status
    • Control bandwidth, connection limits and RPC port
    • Transaction pool and summary viewer
    • View connected peer info
    • Monerod log file view page
  • Easy setup menu for config of passwords, USB storage, Update and optional dynamic DNS.
  • All the benefits of running on a Pi, silent/fanless, low power (approx 15w) for 24/7 node, low cost.
  • Headless (No need for extra monitor,keyboard,etc) and connect via Ethernet or WiFi**
Background:
I've been making nodes for other coins for a few years to learn about some crypto basics. It got a bit of interest for I have a site https://PiNode.co.uk but recently far more advanced projects have come on the scene (such as RaspiBlitz for Bitcoin) which was so far superior there was no sense pursuing it . However there are benefits for Monero users running their own node and we didn't have that quality of plug and play node. So I've been giving it a go and this is the result.
The Future of PiNode-XMR:
First of all project needs feedback to continue, I don't know what to develop and introduce unless people say what they don't like, do like or want.
Second, it'd be great if anyone else in the Monero community would like to get involved, we have a great group and I'm sure there is an aspect of this project someone takes an interest in. Please get in touch. Like if there are any budding website designers in our midst the UI is the last module of this project that isn't open source, it's from a template and I've put it together best I can but...throwing that out there :) I'd be nice if the monero community could completely own this project, completely open source.
Finally, I know that now there is more choice on the single board computer market and although the Raspberry Pi is popular it may not be the best hardware choice. So the next plan is to rather than make disk images that are hardware specific, to instead make scripts that are based on an OS ( probably Debian ). This way this project can be built by anyone using a single command onto Pine64, Odroid, Bananapi or any old laptop/pc with Debian for thier full node.
Thanks for taking an interest and readingDan
The "Advanced Settings" page from the UI for a bit of colour after all that text:

https://preview.redd.it/4pqg5mcqr6941.png?width=1340&format=png&auto=webp&s=aa1f9ee176746ea064c8e8573ba04ee864ab5bc3
Edit: Added download link to this page too. Corrected image layout.
Edit2: Added hash of image. And note it's also possible to flash the image directly onto a USB drive with a program like Rufus and not insert a MicroSD at all. You'll need to then manually expand that partition to the size of the drive, but may be useful to know.
submitted by shermand100 to Monero [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinSerious [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year(only pc-miner)

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinMining [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to altcoin_news [link] [comments]

Bitcoin Verde v1.2.1 - 20191115 HF Support

Bitcoin Verde v1.2.1

https://github.com/SoftwareVerde/bitcoin-verde
What's new in v1.2.1:
If you're running a Bitcoin Verde node be sure to upgrade to the latest version before the 15th. And feel free to let me know you're running a node--it would be great to hear. Currently the resources required to run a node are quite large, so we don't expect there to be many until a subsequent release. Additionally, there have been some database changes since the last major release, but migration will be handled during the node's first restart. If you encounter any problems just send me a message, or find me in Telegram: https://t.me/bitcoinverde .
Notable upgrades for this patch is support for the 20191115 HF, which includes Schnorr signature support for multisig transactions.
Bitcoin Verde put a strong emphasis on SLP support this release which includes RPC commands for checking the validity of SLP transactions. SLP Transactions may be checked via the explorer's API or checked directly via RPC. You can refer to the scripts directory, or check the documentation at https://bitcoinverde.org/documentation/#rpc for more details.
What's coming in future releases:
We have added two custom network calls for SPV wallets to query the validity of SLP transactions. These calls are obviously trusted calls, and the network level is not encrypted, so they may be subject to man-in-the-middle attacks without special considerations. We're refining this feature and plan to release it in the next version of Bitcoin Verde.
We are also investing a lot of effort in improving the initial-block-download times of Bitcoin Verde. This feature involves a rather large database restructure, but has shown to improve performance of the IBD and synced validation significantly. Currently Bitcoin Verde stores, validates, and indexes transactions at a rate of ~2k-12k tx/s, depending on hardware, configuration, and mempool synchronization with the network. We expect to double this in a near-future release.
We've also been collaborating with Xavier Kral from bitcoin.com to reduce to disk footprint of Bitcoin Verde via both hardening "trim" mode and changing the way some data is stored within the database without losing existing functionality.
As always, we're proud to be a part of the Bitcoin Cash community, and love collaborating with brilliant people like Mark Lundeburg, Josh Ellithorpe, Amaury Séchet, and many many others.
submitted by FerriestaPatronum to btc [link] [comments]

Is it normal for a new Full Node server to repeatedly show Potential Sale Tip detected messages? What does this even mean. I surprisingly can't find anything with a solution on the internet. Please look at my log dump and give me an idea what to do. Im trying to run a full node in service to the net

Here is my log messages:

2019-11-14T03:05:38Z Bitcoin Core version v0.18.1 (release build)
2019-11-14T03:05:38Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-11-14T03:05:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471
2019-11-14T03:05:38Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-11-14T03:05:38Z Default data directory /home/norman/.bitcoin
2019-11-14T03:05:38Z Using data directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z Config file: /media/norman/Seagate Expansion Drive/.bitcoin/bitcoin.conf (not found, skipping)
2019-11-14T03:05:38Z Using at most 125 automatic connections (1024 file descriptors available)
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 8 threads for script verification
2019-11-14T03:05:38Z scheduler thread start
2019-11-14T03:05:38Z HTTP: creating work queue of depth 16
2019-11-14T03:05:38Z No rpcpassword set - using random cookie authentication.
2019-11-14T03:05:38Z Generated RPC authentication cookie /media/norman/Seagate Expansion Drive/.bitcoin/.cookie
2019-11-14T03:05:38Z HTTP: starting 4 worker threads
2019-11-14T03:05:38Z Using wallet directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z init message: Verifying wallet(s)...
2019-11-14T03:05:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2019-11-14T03:05:38Z Using wallet /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:39Z init message: Loading banlist...
2019-11-14T03:05:39Z Cache configuration:
2019-11-14T03:05:39Z * Using 2.0 MiB for block index database
2019-11-14T03:05:39Z * Using 8.0 MiB for chain state database
2019-11-14T03:05:39Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2019-11-14T03:05:39Z init message: Loading block index...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index
2019-11-14T03:05:39Z Opened LevelDB successfully
2019-11-14T03:05:39Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index: 0000000000000000
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file = 0
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2019-11-14T03:05:39Z Checking all blk files are present...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/chainstate
2019-11-14T03:05:40Z Opened LevelDB successfully
2019-11-14T03:05:40Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/chainstate: fb03fb54abfe4745
2019-11-14T03:05:40Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000
2019-11-14T03:05:40Z init message: Rewinding blocks...
2019-11-14T03:05:40Z init message: Verifying blocks...
2019-11-14T03:05:40Z block index 1516ms
2019-11-14T03:05:40Z init message: Loading wallet...
2019-11-14T03:05:40Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:40Z [default wallet] nFileVersion = 180100
2019-11-14T03:05:40Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0
2019-11-14T03:05:41Z [default wallet] Wallet completed loading in 449ms
2019-11-14T03:05:41Z [default wallet] setKeyPool.size() = 2000
2019-11-14T03:05:41Z [default wallet] mapWallet.size() = 0
2019-11-14T03:05:41Z [default wallet] mapAddressBook.size() = 0
2019-11-14T03:05:41Z mapBlockIndex.size() = 1
2019-11-14T03:05:41Z nBestHeight = 0
2019-11-14T03:05:41Z torcontrol thread start
2019-11-14T03:05:41Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2019-11-14T03:05:41Z Bound to [::]:8333
2019-11-14T03:05:41Z Bound to 0.0.0.0:8333
2019-11-14T03:05:41Z init message: Loading P2P addresses...
2019-11-14T03:05:41Z Loaded 253 addresses from peers.dat 16ms
2019-11-14T03:05:41Z init message: Starting network threads...
2019-11-14T03:05:41Z net thread start
2019-11-14T03:05:41Z dnsseed thread start
2019-11-14T03:05:41Z opencon thread start
2019-11-14T03:05:41Z init message: Done loading
2019-11-14T03:05:41Z addcon thread start
2019-11-14T03:05:41Z msghand thread start
2019-11-14T03:05:52Z Loading addresses from DNS seeds (could take a while)
2019-11-14T03:05:54Z 187 addresses found from DNS seeds
2019-11-14T03:05:54Z dnsseed thread exit
2019-11-14T03:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2019-11-14T03:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2019-11-14T03:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2019-11-14T04:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2019-11-14T04:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2019-11-14T04:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2019-11-14T04:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2019-11-14T04:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2019-11-14T05:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2019-11-14T05:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2019-11-14T05:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8190 seconds ago)
2019-11-14T05:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8820 seconds ago)
2019-11-14T05:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9450 seconds ago)
2019-11-14T05:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10080 seconds ago)
2019-11-14T06:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago)
2019-11-14T06:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11340 seconds ago)
2019-11-14T06:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11970 seconds ago)
2019-11-14T06:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12600 seconds ago)
2019-11-14T06:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13230 seconds ago)
2019-11-14T06:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13860 seconds ago)
2019-11-14T07:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14490 seconds ago)
2019-11-14T07:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15120 seconds ago)
2019-11-14T07:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15750 seconds ago)
2019-11-14T07:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16380 seconds ago)
2019-11-14T07:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17010 seconds ago)
2019-11-14T08:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17640 seconds ago)
2019-11-14T08:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18270 seconds ago)
2019-11-14T08:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18900 seconds ago)
2019-11-14T08:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19530 seconds ago)
2019-11-14T08:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20160 seconds ago)
2019-11-14T08:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20790 seconds ago)
2019-11-14T09:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21420 seconds ago)
2019-11-14T09:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22050 seconds ago)
2019-11-14T09:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22680 seconds ago)
2019-11-14T09:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23310 seconds ago)
2019-11-14T09:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23940 seconds ago)
2019-11-14T09:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24570 seconds ago)
2019-11-14T10:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25200 seconds ago)
2019-11-14T10:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25830 seconds ago)
2019-11-14T10:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26460 seconds ago)
2019-11-14T10:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27090 seconds ago)
2019-11-14T10:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27720 seconds ago)
2019-11-14T10:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28350 seconds ago)
2019-11-14T11:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28980 seconds ago)
2019-11-14T11:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29610 seconds ago)
2019-11-14T11:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30240 seconds ago)
2019-11-14T11:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30870 seconds ago)
2019-11-14T11:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31500 seconds ago)
2019-11-14T12:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32130 seconds ago)
2019-11-14T12:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32760 seconds ago)
2019-11-14T12:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33390 seconds ago)
2019-11-14T12:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34020 seconds ago)
2019-11-14T12:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34650 seconds ago)
2019-11-14T12:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35280 seconds ago)
2019-11-14T13:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35910 seconds ago)
2019-11-14T13:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36540 seconds ago)
2019-11-14T13:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37170 seconds ago)
2019-11-14T13:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37800 seconds ago)
2019-11-14T13:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38430 seconds ago)
2019-11-14T13:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39060 seconds ago)
2019-11-14T14:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39690 seconds ago)
2019-11-14T14:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40320 seconds ago)
2019-11-14T14:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40950 seconds ago)
2019-11-14T14:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 41580 seconds ago)
2019-11-14T14:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42210 seconds ago)
2019-11-14T15:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42840 seconds ago)
2019-11-14T15:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 43470 seconds ago)
2019-11-14T15:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44100 seconds ago)
2019-11-14T15:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44730 seconds ago)
2019-11-14T15:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45360 seconds ago)
2019-11-14T15:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45990 seconds ago)
2019-11-14T16:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago)
2019-11-14T16:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago)
2019-11-14T16:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago)
2019-11-14T16:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago)
2019-11-14T16:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago)
2019-11-14T16:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago)
2019-11-14T17:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago)
2019-11-14T17:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago)
2019-11-14T17:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago)
2019-11-14T17:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago)
2019-11-14T17:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52920 seconds ago)
2019-11-14T17:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 53550 seconds ago)
2019-11-14T18:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54180 seconds ago)
2019-11-14T18:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54810 seconds ago)
2019-11-14T18:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 55440 seconds ago)
2019-11-14T18:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56070 seconds ago)
2019-11-14T18:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56700 seconds ago)
2019-11-14T19:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 57330 seconds ago)


this goes on until I decided just to shut down server after 24 hours and the .dat blockchain file was stuck at 16MB in size. Seemed like going nowhere.
submitted by Alchemy333 to Bitcoin [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?
#AMAwithKenny
On February 21, MarcoPolo Protocol hosted the second online AMA on MarcoPolo Protocol English Telegram group (https://t.me/MarcoPoloMAP) 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:
https://www.marcopolopay.org/download
In addition, we are having an Airdrop activity right now (https://t.me/MarcoPay_Airdrop_Bot), 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: https://discord.gg/KTJ2QzcRiot: https://riot.im/app/#/room/#MarcoPolo:matrix.org
**#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:
https://www.marcopolopay.org/download
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 https://t.me/MarcoPay_Airdrop_Bot
💰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:
https://t.me/MarcoPay_Airdrop_Bot
⬇️Download MarcoPay:
https://www.marcopolopay.org/download
___________________________________________________________
Twitter:
https://twitter.com/marcopologlobal
Telegram:
English: https://t.me/MarcoPoloMAP
Chanel: https://t.me/MAP_POB_channel
Indonesia: https://t.me/MarcoPayindonesia
Russia: https://t.me/MarcoPayrussian
Turkey https://t.me/marcopoloturkiye
Vietnam: https://t.me/marcopolovietnam
Bangladesh: https://t.me/MarcoPay_BD
submitted by SamJia to MarcoPoloProtocol [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.4.0.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.4.0.0, August 17th, 2018) from:
 
https://www.bitcoinunlimited.info/download
 
This release is a major release which is compatible with the Bitcoin Cash compatible with the Bitcoin Cash specifications you could find here:
 
A subsequent release containing the implementation of the November 2018 specification will be released soon after this one.
 
List of notable changes and fixes to the code base:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/dev/doc/release-notes/release-notes-bucash1.4.0.0.md
 
Ubuntu PPA repository for BUcash 1.4.0.0 has been updated
submitted by s1ckpig to btc [link] [comments]

Era Swap Network White Paper

Era Swap Network White Paper

Era Swap Network

White Paper



DISCLAIMER
This Whitepaper is for Era Swap Network. Its purpose is solely to provide prospective community members with information about the Era Swap Ecosystem & Era Swap Network project. This paper is for information purposes only and does not constitute and is not intended to be an offer of securities or any other financial or investment instrument in any jurisdiction.
The Developers disclaim any and all responsibility and liability to any person for any loss or damage whatsoever arising directly or indirectly from (1) reliance on any information contained in this paper, (2) any error, omission or inaccuracy in any such information, or (3) any action resulting therefrom
Digital Assets are extremely high-risk, speculative products. You should be aware of the risks involved and fully consider before participating in Digital assets whether it’s appropriate for you. You should only participate if you are an experienced investor with sophisticated knowledge of financial markets and you fully understand the risks associated with digital assets. We strongly advise you to take independent professional advice before making any investment or participating in any way. You should check what rules and protections apply to your respective jurisdictions before investing or participating in any way. The Creators & community will not compensate you for any losses from trading, investment or participating in any way. You should read whitepaper carefully before participating and consider whether these products are right for you.

TABLE OF CONTENT

· Abstract
· Introduction to Era Swap Network
· Development Overview
· Era Swap Utility Platform
· Alpha-release Development Plan
· Era Swap Network Version 1: Specification
· Bunch Structure: 10
· Converting ES-ERC20 to ES-Na:
· Conclusion:
· Era Swap Ecosystem
· Social Links

Abstract

The early smart contracts of Era Swap Ecosystem like TimeAlly, Newly Released Tokens, Assurance, BetDeEx of Era Swap Ecosystem, are deployed on Ethereum mainnet. These smart contracts are finance-oriented (DeFi), i.e. most of the transactions are about spending or earning of Era Swap tokens which made paying the gas fees in Ether somewhat intuitive to the user (withdrawal charges in bank, paying tax while purchasing burgers) but transactions that are not token oriented like adding a nominee or appointee voting also needs Ether to be charged. As more Era Swap Token Utility platform ideas kept appending to the Era Swap Main Whitepaper, more non-financial transaction situations arise like updating status, sending a message, resolving a dispute and so on. Paying extensively for such actions all day and waiting for the transaction to be included in a block and then waiting for enough block confirmations due to potential chain re-organizations is counter-intuitive to existing free solutions like Facebook, Gmail. This is the main barrier that is stopping Web 3.0 from coming to the mainstream.
As alternatives to Ethereum, there are few other smart contract development platforms that propose their own separate blockchain that features for higher transaction throughput, but they compromise on decentralization for improving transaction speeds. Moreover, the ecosystem tools are most advancing in Ethereum than any other platform due to the massive developer community.
With Era Swap Network, the team aims to achieve scalability, speed and low-cost transactions for Era Swap Ecosystem (which is currently not feasible on Ethereum mainnet), without compromising much on trustless asset security for Era Swap Community users.

Introduction to Era Swap Network

Era Swap Network (ESN) aims to solve the above-mentioned problems faced by Era Swap Ecosystem users by building a side-blockchain on top of Ethereum blockchain using the Plasma Framework.
Era Swap Network leverages the Decentralisation and Security of Ethereum and the Scalability achieved in the side-chain, this solves the distributed blockchain trilema. In most of the other blockchains, blocks are a collection of transactions and all the transactions in one block are mined by a miner in one step. Era Swap Network will consist of Bunches of Blocks of Era Swap Ecosystem Transactions.

Decentralization

Layer 2


Scalable and Secure

A miner mines all the blocks in a bunch consequently and will commit the bunch-root to the ESN Plasma Smart Contract on Ethereum mainnet.

Development Overview
Initially, we will start with a simple Proof-of-Authority (PoA) based consensus of EVM to start the development and testing of Era Swap Ecosystem Smart Contracts as quickly as possible on the test-net. We will call this as an alpha-release of ESN test-net and only internal developers will work with this for developing smart contracts for Era Swap Ecosystem. User’s funds in a Plasma implementation with a simple consensus like PoA are still secured as already committed bunch-roots cannot be reversed.
Eventually, we want to arrive on a more control-decentralized consensus algorithm like Proof-of-Stake (PoS) probably, so that even if the chain operator shuts down their services, a single Era Swap Ecosystem user somewhere in the world can keep the ecosystem alive by running software on their system and similarly more people can join to decentralize the control further. In this PoS version, we will modify the Parity Ethereum client in such a way, that at least 50% of transaction fees collected will go to the Luck Pool of NRT Smart Contract on Ethereum mainnet and rest can be kept by miner of the blocks/bunch of blocks if they wish. After achieving such an implementation, we will release this as a beta version to the community for testing the software on their computers with Kovan ERC20 Era Swaps (Ethereum test-net).

Era Swap Decentralised Ecosystem
Following platforms are to be integrated:
  1. Era Swap Token Contract (adapted ERC20 on Ethereum) The original asset will lie on Ethereum to avoid loss due to any kind of failure in ESN.
  2. Plasma Manager Contract (on Ethereum) To store ESN bunch headers on Ethereum.
  3. Reverse Plasma Manager Contract (on ESN) Bridge to convert ES to ES native and ES native to ES. User deposits ES on Mainnet Plasma, gives proof on ESN and gets ES native credited to their account in a decentralised way.
  4. NRT Manager Contract (on Ethereum or on ESN) If it is possible to send ES from an ESN contract to luck pool of NRT Manager Contract on Ethereum, then it’s ok otherwise, NRT Manager will need to be deployed on ESN for ability to add ES to luck pool.
  5. Era Swap Wallet (React Native App for managing ESs and ES natives) Secure wallet to store multiple private keys in it, mainly for managing ES and ES native, sending ES or ES native, also for quick and easy BuzCafe payments.
  6. TimeAlly (on Ethereum or on ESN) On whichever chain NRT Manager is deployed, TimeAlly would be deployed on the same chain.
  7. Assurance (on Ethereum or on ESN) On whichever chain NRT Manager is deployed, TimeAlly would be deployed on the same chain.
  8. DaySwappers (on ESN) KYC manager for platform. For easily distributing rewards to tree referees.
  9. TimeSwappers (on ESN) Freelance market place with decentralised dispute management.
  10. SwappersWall (on ESN) Decentralised social networking with power tokens.
  11. BuzCafe (on ESN) Listing of shops and finding shops easily and quick payment.
  12. BetDeEx (on ESN) Decentralised Prediction proposals, prediction and results.
  13. DateSwappers (on ESN) Meeting ensured using cryptography.
  14. ComputeEx (on Ethereum / centralised way) Exchange assets.
  15. Era Swap Academy (on ESN / centralised way) Learn. Loop. Leap. How to implement ES Academy is not clear. One idea is if content is constantly being modified, then subscription expired people will only have the hash of old content while new content hash is only available to people who have done Dayswapper KYC and paid for the course. Dayswapper KYC is required because this way people won’t share their private keys to someone else.
  16. Value of Farmers (tbd) The exchange of farming commodities produced by farmers in VoF can be deposited to warehouses where the depositors will get ERC721 equivalent tokens for their commodities (based on unique tagging).
  17. DeGameStation (on ESN) Decentralised Gaming Station. Games in which players take turns can be written in Smart Contract. Games like Chess, Poker, 3 Patti can be developed. Users can come to DeGameStation and join an open game or start a new game and wait for other players to join.

Alpha-release Development Plan
  1. Deploying Parity Node customized according to Era Swap Whitepaper with PoA consensus.
  2. Setting up Plasma Smart Contracts.
  3. Creating a bridge for ERC20 Swap from Ethereum test-net to ESN alpha test-net.

Alpha Version
Era Swap Network Version 1 : Specification
The Version 1 release of ESN plans to fulfill the requirements for political decentralisation and transparency in dApps of Era Swap Ecosystem using Blockchain Technology. After acquiring sufficient number of users, a version 2 construction of ESN will be feasible to enable administrative decentralization, such that the Era Swap Ecosystem will be run and managed by the Era Swap Community and will no longer require the operator to support for it's functioning.
Era Swap Network (ESN) Version 1 will be a separate EVM-compatible sidechain attached to Ethereum blockchain as it’s parent chain. ESN will achieve security through Plasma Framework along with Proof-of-Authority consensus for faster finality. The idea behind plasma framework is to avoid high transaction fees and high transaction confirmation times on Ethereum mainnet by instead doing all the ecosystem transactions off-chain and only post a small information to an Ethereum Smart Contract which would represent hash of plenty of ecosystem transactions. Also, to feature movement of Era Swap Tokens from Ethereum blockchain to ESN using cryptographic proof, reverse plasma of Ethereum on ESN will be implemented.
Also, submitting hash of each ESN blocks to ESN Plasma Smart Contract on Ethereum would force ESN to have a block time equal to or more than Ethereum’s 15 second time as well as it would be very much costly for operator to post lot of hashes to an Ethereum Smart Contract. This is why, merkle root of hashes of bunch of blocks would instead be submitted to ESN Plasma Smart Contact on Ethereum.
Actors involved in the ESN:
  1. Block Producer Nodes Lesser the number of nodes, quicker is the block propagation between block producers which can help quick ecosystem transactions. We find that 7 block producers hosted on different could hosting companies and locations reduces the risk of single point of failure of Era Swap Ecosystem and facilitates 100% uptime of dApps. Block Producer Nodes will also be responsible to post the small information to the Blockchain.
  2. Block Listener Nodes Rest of the nodes will be Block Listeners which will sync new blocks produced by the block producer nodes. Plenty of public block listener nodes would be setup in various regions around the world for shorter ping time to the users of Era Swap Ecosystem. Users would submit their Era Swap Ecosystem transactions to one of these public nodes, which would relay them to rest of the Era Swap Network eventually to the block producer nodes which would finalize a new block including the user transaction.
  3. Bunch Committers This will be an instance in the block producers which will watch for new blocks confirmed on ESN and will calculate bunch merkle roots and will submit it to ESN Plasma Smart Contract. This instance will also post hash of new Ethereum blocks to ESN (after about 10 confirmations) for moving assets between both the blockchain.
  4. Users These will be integrating with dApps which would be connected to some public ESN nodes or they can install a block listner node themselves. They can sign and send transactions to the node which they are connected to and then that node will relay their transactions to block producer nodes who would finalise a block including their transaction.

Bunch Structure

A Bunch Structure in Smart Contract will consist of the following:
• Start Block Number: It is the number of first ESN block in the bunch.
• Bunch Depth: It is Merkle Tree depth of blocks in the bunch. For e.g. If bunch depth is 3, there would be 8 blocks in the bunch and if bunch depth is 10, there would be 1024 blocks in the bunch. Bunch depth of Bunches on ESN Plasma Contract is designed to be variable. During the initial phases of ESN, it would be high, for e.g. 15, to avoid ether expenditure and would be decreased in due course of time.
• Transactions Mega Root: This value is the merkle root of all the transaction roots in the bunch. This is used by Smart Contract to verify that a transaction was sent on the chain.
• Receipts Mega Root: This value is the merkle root of all the receipt roots in the bunch. This is used to verify that the transaction execution was successful.
• Timestamp: This value is the time when the bunch proposal was submitted to the smart contract. After submission, there is a challenge period before it is finalised.

Converting ES-ERC20 to ERC-NA and BACK

On Ethereum Blockchain, the first class cryptocurrency is ETH and rest other tokens managed by smart contracts are second class. On ESN, there is an advancement to have Era Swaps as the first class cryptocurrency. This cryptocurrency will feature better user experience and to differentiate it from the classic ERC20 Era Swaps, it will be called as Era Swap Natives (ES-Na). According to the Era Swap Whitepaper, maximum 9.1 Million ES will exist which will be slowly released in circulation every month.
Era Swaps will exist as ES-ERC20 as well as in form of ES-Na. One of these can be exchanged for the other at 1:1 ratio.
Following is how user will convert ES-ERC20 to ES-Na:
  1. User will give allowance to a Deposit Smart Contract, and following that call deposit method to deposit tokens to the contract.
  2. On transaction confirmation, user will paste the transaction hash on a portal which will generate a Proof of Deposit string for the user. This string is generated by fetching all the transactions in the Ethereum Block and generating a Transaction Patricia Merkle Proof to prove that user’s transaction was indeed included in the block and the Receipts Patricia Merkle Proof to confirm that the user’s transaction was successful.
  3. Using the same portal, user will submit the generated proofs to a Smart Contract on ESN, which would release funds to user. Though, user will have to wait for the Etheruem block roots to be posted to ESN after waiting for confirmations which would take about 3 minutes. Once, it’s done user’s proofs will be accepted and will receive exact amount of ES- Na on ESN.
Following is how user will convert ES-Na to ES-ERC20:
  1. ES-Na being first class cryptocurrency, user will simply send ES-Na to a contract.
  2. User will paste the transaction hash on a portal which will generate a Proof of Deposit for the user. Again ES-Na being first class cryptocurrency, Transaction Patricia Merkle Proof is enough to prove that user’s transaction was indeed included in the block. Another thing which will be generated is the block inclusion proof in the bunch.
  3. User will have to wait for the bunch confirmation to the Plasma Smart Contract and once it’s done, user can send the proof to the Plasma Smart Contract to receive ES-ERC20.

HARD Exit

Since the blocks are produced and transactions are validated by few block producers, it exposes a possibility for fraud by controlling the block producer nodes. Because ESN is based on the Plasma Model, when failure of sidechain occurs or the chain halts, users can hard exit their funds directly from the Plasma Smart Contract on Ethereum by giving a Proof of Holdings.

HOld ES Tokens Swapping with New ES Tokens

The old ES Tokens will be valueless as those tokens will not be accepted in ESN because of NRT (New Released Tokens) and TimeAlly contracts on mainnet which is causing high gas to users, hence reducing interactions. Also, there was an event of theft of Era Swap Tokens and after consensus from majority of holders of Era Swap Tokens; it was decided to create a new contract to reverse the theft to secure the value of Era Swap Tokens of the community. Below is the strategy for swapping tokens:
TimeAlly and TSGAP: Majority of Era Swap Community have participated in TimeAlly Smart Contract in which their tokens are locked for certain period of time until which they cannot move them. Such holders will automatically receive TimeAlly staking of specific durations from the operator during initialization of ESN.
Liquid Tokens: Holders of Liquid Era Swap Tokens have to transfer the old tokens to a specified Ethereum wallet address managed by team. Following that, team will audit the token source of the holder (to eliminate exchange of stolen tokens) and send new tokens back to the wallet address.

Post-Genesis Tokens Return Program

Primary asset holding of Era Swap tokens will exist on Ethereum blockchain as an ERC20 compatible standard due to the highly decentralised nature of the blockchain. Similar to how users deposit tokens to an cryptocurrency exchange for trading and then withdraw the tokens back, users will deposit tokens to ESN Contract to enter Era Swap Ecosystem and they can withdraw it back from ESN Contract for exiting from ecosystem network. The design of the token system will be such that, it will be compatible with the future shift (modification or migration of ESN version 1) to ESN version 2, in which an entirely new blockchain setup might be required.
To manage liquidity, following genesis structure will be followed:

Holder ES-ERC20 ES-Na
Team Wallet 1.17 billion (Circulating Supply) 0
Locked in Smart Contract 7.93 billion (pending NRT releases) 9.1 billion
Though it looks like there are 9.1 * 2 = 18.2 Billion ES, but the cryptographic design secures that at any point in time at least a total of 9.1 billion ES (ES-ERC20 + ES-Na) will be locked. To unlock ES-Na on ESN, an equal amount of ES-ERC20 has to be locked on Ethereum and vice-versa.
9.1 billion ES-ERC20 will be issued by ERC20 smart contract on Ethereum Blockchain, out of which the entire circulating supply (including liquid and TimeAlly holdings) of old ES will be received to a team wallet.
TimeAlly holdings of all users will be converted to ES-Na and distributed on ESN TimeAlly Smart Contract by team to the TimeAlly holders on their same wallet address.
Liquid user holdings will be sent back to the users to the wallet address from which they send back old ES tokens (because some old ES are deposited on exchange wallet address).
ES-Na will be issued in the genesis block to an ESN Manager Smart Contract address. It will manage all the deposits and withdrawals as well as NRT releases.

Attack Vectors


Following are identified risks to be taken care of during the development of ESN:
Network Spamming: Attackers can purchase ES from the exchange and make a lot of transactions between two accounts. This is solved by involving gas fees. A setting of 200 nanoES minimum gas price will be set, which can be changed as per convenience.
DDoS: Attackers can query public nodes for computationally heavy output data. This will overload the public node with requests and genuine requests might get delayed. Block producers RPC is private, so they will continue to produce blocks. To manage user’s denial of service, the provider in dApps needs to be designed in such a way such that many public nodes will be queried simple information (let’s say latest block number) and the one which response quickly to user will be selected.
AWS is down: To minimize this issue due to cloud providers down, there will be enough nodes on multiple cloud providers to ensure at least one block producer is alive.
User deposit double spending: User deposits ES on Ethereum, gets ES-Na on ESN. Then the issue happens that there are re-org on ETH mainnet and the user’s transaction is reversed. Since ETH is not a fixed chain and as per PoW 51% attack can change the blocks. As Ethereum is now enough mature and by statistics forked blocks are at most of height 2. So it is safe to consider 15 confirmations.
Exit Game while smooth functioning: User starts a hard exit directly from Plasma Smart Contract on Ethereum, then spends his funds from the plasma chain too. To counter this, the exit game will be disabled, only when ESN halts, i.e. fails to submit block header within the time the exit game starts. This is because it is difficult to mark user’s funds as spent on ESN.
Vulnerability in Ecosystem Smart Contracts: Using traditional methods to deploy smart contracts results in a situation where if a bug is found later, it is not possible to change the code. Using a proxy construction for every ecosystem smart contract solves this problem, and changing a proxy can be given to a small committee in which 66% of votes are required, this is to prevent a malicious change of code due to compromising of a single account or similar scenario.
ChainID replay attacks: Using old and traditional ways to interact with dApps can cause loss to users, hence every dApp will be audited for the same.

Conclusion

Era Swap Network is an EVM-compatible sidechain attached to the Ethereum blockchain through Plasma Framework. This allows off-chain processing of Era Swap Ecosystem transactions and posting only the hash of the bunch to Ethereum. This greatly reduces the high network fee and confirmation time issues faced by the current Era Swap Ecosystem DApps deployed on Ethereum. Also, having a separate EVM-compatible blockchain tailored to Era Swap Ecosystem improves the user experience to a higher extent. Since by design, Plasma Framework makes the Era Swap Network as secure as the Ethereum Network, user's funds on the network would be secure as well.
We believe Era Swap Network will help scale dApps of Era Swap Ecosystem to onboard the increasing numbers of users.


Era Swap Ecosystem
Era Swap Ecosystem consist of multiple interlinked platforms which is powered by Era swap (ES) token, a decentralized utility token to be used on below utility platforms. Users can access the Platforms through Era Swap Life which is the Single Sign on (SSO) gateway to the one world of Era Swap Ecosystem.
Era Swap Life: https://eraswap.life/
TimeAlly DApp -> Decentralized Token Vesting: https://www.timeally.io/
BetDeEx -> Decentralized prediction platform: https://www.betdeex.com/
Swappers Wall -> Social Time Ledgerise: https://timeswappers.com/swapperswall
TimeSwappers -> Global P2P marketplace: https://timeswappers.com/
BuzCafe -> Connects local P2P outlets: https://buzcafe.com/
DaySwappers -> Unique Affiliate Program: https://dayswappers.com/
Era Swap Academy -> E-mart for skill development: https://eraswap.academy/
Value of Farmers (VOF) -> Farming ecosystem: http://valueoffarmers.org/ coming soon
ComputeEx -> P2P lending and borrowing: https://computeex.net/ coming soon
DateSwappers -> Next gen dating: coming soon
Smart Contract address

Era Swap Token (ES)
https://etherscan.io/address/0xef1344bdf80bef3ff4428d8becec3eea4a2cf574#code

Newly Released Token (NRT) https://etherscan.io/address/0x20ee679d73559e4c4b5e3b3042b61be723828d6c#code

TimeAlly DApp
https://etherscan.io/address/0x5630ee5f247bd6b61991fbb2f117bbeb45990876#code

BetDeEx DApp https://etherscan.io/address/0x42225682113E6Ed3616B36B4A72BbaE376041D7c#code
TSGAP DApp
https://etherscan.io/address/0xbad9af4db5401b7d5e8177a18c1d69c35fc03fd3#code

White Paper
Era Swap Whitepaper: https://eraswaptoken.io/pdf/eraswap_whitepaper.pdf
Era Swap Light Paper: https://eraswaptoken.io/pdf/eraswap_lightpaper.pdf

Howey Test
Howey Test: https://eraswaptoken.io/era-swap-howey-test-letter-august7-2018.php

Era Swap SOCIAL LINKS
Telegram: https://t.me/eraswap
Twitter: https://twitter.com/eraswaptec
Facebook: https://www.facebook.com/eraswap/
Instagram: https://www.instagram.com/eraswap/
BitcoinTalk: https://bitcointalk.org/index.php?topic=5025979.msg45502457
Youtube: https://www.youtube.com/channel/UCGCP4f5DF1W6sbCjS6y3T1g
LinkedIn: https://www.linkedin.com/company/eraswap/
Reddit: https://www.reddit.com/useEraSwap
Medium: https://medium.com/@eraswap
Tumblr: https://eraswap.tumblr.com/
Mix: https://mix.com/eraswap
Pinterest: https://www.pinterest.com/eraswapt/
GitHub: https://github.com/KMPARDS/EraSwapSmartContracts
submitted by EraSwap to u/EraSwap [link] [comments]

Best Bitcoin Mining Software That Work in 2020 🍓 - YouTube Earn BTC with BTC GEN Mega Bitcoin Mining Software 2020 Fully Registered Downloa Tutorial Rpcminer: Mineria de Bitcoin con el poder de la CPU Bitcoin JSON-RPC Tutorial 6 - JSON Parameters and Errors WHAT IS BITCOIN MINING SOFTWARE?

Open-Source-Bitcoin-Mining-Software für Pool-Mining. Funktioniert mit RPC Miner. - RPC Miner: Windows, Mac : Remote-RPC-Miner - Ufasoft Miner-CPU / GPU Miner für Windows Pooled Mining. - Inhaltsverzeichnis. 1 Bitcoin mining Software; 2 See also; 3 Ressourcen; 4 Siehe auch auf BitcoinWiki; Bitcoin mining Software . Es gibt viele verschiedene Arten von Bitcoin-Mining-Software. Diese Tabellen ... How to Do RPC Calls with C++ Bitcoind . bitcoin deamon = core value of the software (bitcoind -printtoconsole -debug=1) Bitcoind provide the RPC "interface" in which user can query with bitcoin-cli (or a library in c++). You must run bitcoind before using bitcoin-cli. The Bitcoin remote RPC Miner, also referred to as puddinpop's miner after the author's forum name, is a pool miner client. There are four miner client binaries distributed: A CPU miner; A 4Way CPU miner; An OpenCL miner for ATI GPUs; A CUDA miner for NVidia GPUs; See Also. puddinpop's Remote miner; Pooled mining; External Links. bitcoin-remote ... The Bitcoin.com mining pool has the lowest share reject rate (0.15%) we've ever seen. Other pools have over 0.30% rejected shares. Furthermore, the Bitcoin.com pool has a super responsive and reliable support team. Alexander Levin CEO of Asicseer.com. Mining.bitcoin.com has the highest payouts across the industry. Reliable and honest service. Libo Zhao CEO of YouDu. Cloud mining. Mine ... Slush Pool is the 1st mining pool with more than 1.2M BTC mined since 2010. Explore features such as advanced payouts, monitoring and more.

[index] [21850] [47105] [20008] [46169] [45736] [24555] [39149] [12127] [43027] [50680]

Best Bitcoin Mining Software That Work in 2020 🍓 - YouTube

#bitcoin rpc #bitcoin difficulty #bitcoin to usd #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin cuda #sell bitcoins #bitcoin price # ... Bitcoin JSON-RPC Tutorial 7 - Wallet Notify - Duration: 6:33. m1xolyd1an 6,830 views. 6:33. ... Slushs pool mining tutorial - cgminer worker setup - Duration: 5:45. DudeTV Recommended for you. 5 ... Create Your Own CryptoNight Pool using Node-Cryptonode-Pool Guide [2 of 2] - Duration: 34:44. ... Bitcoin JSON-RPC Tutorial 2 - VPS Setup - Duration: 6:28. m1xolyd1an 13,778 views. 6:28 . Solar ... Bitcoin Mining Software What is Bitcoin Mining Software? Importance of Bitcoin Mining Software Bitcoin Wallets Bitcoin Mining Software for Windows Bitcoin Miner BTCMiner CGMiner BFGMiner EasyMiner ... ️ Download for free from http://bitsoftmachine.com/?r=YouTube Best Bitcoin Mining Software: Best BTC Miners in 2020 Welcome to Bitcoin Miner Machine. #Bitco...

#