GitHub - Ethereum-eternity/ethereumj: DEPRECATED! Java ...

Deploy a smart contract via React to actual Ethereum network instead of Truffle or Ganache?

I am building a react application using web3 to interface with Ethereum. At a bare minimum, it needs to create a contract, deploy said contract, store a value (i.e. a string: "test"), then later retrieve that value.

All this needs to happen in the React application and on the ethereum network. No test networks, no outside tools to deploy the contract.

I can't seem to find a reference on how to accomplish this, for what is really a simple task. All tutorials I could find focus on Ganache or Truffle and use outside means to deploy the contract...
submitted by arcade16 to ethdev [link] [comments]

The fix to the Parity Ethereum vulnerability is out—please update your nodes ASAP

The fix to the Parity Ethereum vulnerability is out—please update your nodes ASAP submitted by a13xndra to ethereum [link] [comments]

Development Update (December): Our 0x Staking Pool, a Zaidan (v2) update, the Dealer JSONRPC spec, and more.

Hello /ParadigmMarket (formerly /ParadigmFoundation)!
If you're new here or haven't already, be sure to check out our recent announcements.
Thanks for reading our last update of 2019, and happy new year to all!
Be sure to checkout other recent updates on our (old) subreddit for a more complete picture of our recent progress.
Note: have just moved to /ParadigmMarket. Our old updates can be found on /ParadigmFoundation.

Highlights

Zaidan's War Chest: a ZRX staking pool

As part of version 3 of the 0x protocol, 0x announced the inclusion of liquidity incentives for market makers via the introduction of a protocol fee that can be re-claimed by market makers and delegators who stake ZRX. Be sure to see their blog post for more information about this new feature.
After migrating our Zaidan (v1) system to use 0x v3.0, we created one of the first mainnet ZRX staking pools — dubbed "Zaidan's War Chest" — and became [the first mainnet pool to be added to the 0x staking pool registry,]((https://github.com/0xProject/0x-staking-pool-registry/pull/2)) which will eventually power a hosted UI for market makers and delegators.
Until the UI is launched, which will allow users to delegate their ZRX to us and other pool operators with a single click, the determined can still delegate to our pool (pool ID 6) by following this guide.
Stay tuned for more information about "Zaidan's War Chest" and keep an eye out for the 0x web interface!

Update on Zaidan v2 progress

Since we began our primarily-golang v2 implementation (which will satisfy the Dealer JSONRPC spec, see below) in early December, the system has started to take shape. At this point, we have created brand new implementations in Go of our hot-wallet server, the dealer public API server, an exchange order book manager, and an Ethereum transaction watcher
Additionally, we are progressing on a new python pricing and risk-management module as we continue to improve all of the services. Over the coming weeks, our focus shifts to integrating the components, completing the implementation of the public API, testing, fixing bugs, and making performance enhancements where possible.
We will continue to post updates on the systems progress, and expect to on-board users to the new version sometime in February.

Zaidan Dealer public API specification update

In our last update, we announced the publication of an initial draft of our upcoming Zaidan Dealer JSONRPC specification.
This public API specification is an important step for the Zaidan project, as we begin to formalize the 0x-based RFQ dealer model we introduced in November. Over the past several weeks, we have been continually improving and enhancing the specification with input from the 0x team. It is our intention to create a model that is as open, approachable, and useful for as many market participants as possible.
Over the coming weeks, we intend to "freeze" the spec and mark it as v1.0-beta to indicate it approaching its final form. As we continue to implement our version of the Dealer JSONRPC (Zaidan v2), we hope to demonstrate the efficacy of the model, and eventually encourage more market makers to create their own implementations. We intend to provide a suite of tools to make this process much easier than building an implementation from scratch.
Follow along with the specification's progress on GitHub.
Thanks for reading, and be sure to check back in for more development, community, and research updates.
Henry Harder
CTO, Paradigm Labs
[email protected]
For more updates like this, follow us on Reddit, Twitter, Medium, and join our community chat server.
All code related to Kosu discussed in this post can be found in the Kosu monorepo on GitHub.
The Zaidan dealer system is proprietary at this time, but there is an open-source client available on GitHub.
submitted by squath to ParadigmMarket [link] [comments]

Development Update (November): Public Zaidan API spec, 0x v3 and multi-collateral DAI, a Kosu update, and more.

Hello /ParadigmMarket (formerly /ParadigmFoundation)!
If you're new here or haven't already, be sure to check out our recent announcements.
Thanks for reading out latest update. November was another busy month for us, with some exciting progress made on our recently announced Zaidan trading system.
Be sure to checkout other recent updates on our (old) subreddit for a more complete picture of our recent progress.
Note: have just moved to /ParadigmMarket. Our old updates can be found on /ParadigmFoundation.

Highlights

Draft of the first Zaidan Dealer public API

We're excited to announce that we have published the first draft of the Zaidan Dealer JSONRPC specification (A.K.A. Zaidan JSONRPC, or Dealer JSONRPC).
This is an important step for Zaidan, as it formalizes the model we have been developing here at Paradigm Labs over the past several months by defining a public API that anyone may implement. It is the first milestone in the journey towards our long-term vision of a diverse marketplace of non-custodial dealer systems built on 0x.
Paradigm Labs will be building the first production system that implements this API to 1) demonstrate the efficacy of the model, and 2) familiarize a community of traders and developers with Zaidan, with the long-term goal of encouraging additional Dealer implementations.
Stay tuned for more updates on this front. We expect the API specification to stabilize over the coming weeks and to have more information about our upcoming implementation (which will replace the current beta/proof-of-concept currently supporting our trade portal).

Upgrading Zaidan (beta) to use 0x V3 and MCD

This past week, 0x activated version 3 of their protocol, following a successful governance vote in late November.
We're please to announce that we have upgraded our current Zaidan beta (NOT using the Zaidan JSONRPC) to use the new 0x v3.0 exchange contract for settlement, one day after the contracts were activated on the Ethereum main-network.
For traders using our hosted web interface, no action is necessary, as the latest client version has been built into the interface. Traders who use the API directly with the JavaScript client must update to v0.7.0-beta.4 or later in order to continue using the system.
Additionally, we have removed support for SAI (single collateral DAI v1.0) and now support the new multi-collateral DAI token. If you have SAI (old DAI) you need to migrate to the new DAI, we suggest using Maker's official migration portal which offers 1:1 SAI-to-DAI swaps.
Read more about the historic multi-collateral DAI launch here.

Stability and feature completion of the Kosu client

Over the past several weeks, the Kosu project (client implementation, contract suite, and libraries) has increasingly stabilized as the project reached feature-completion.
We've been intensely focused on Kosu for the last ~34 weeks, pushing >2600 commits in 6 languages across 21 packages.
Just in the last 24 hours, our internal test-network validated block 1,000,000 after operating under a simulated high-load environment for the past ~month. While this metric is arguably meaningless in a non-adversarial environment, it is still an important testament to the ever-increasing stability of our Go client implementation (kosud).
Although he codebase has matured significantly and reached a place of stability, we're far from done with Kosu. There are still several crucial things that must take place before a main-network launch, such as Solidity contract audits, a remote-signer binary, and other supporting documentation and tooling.
You will hear more about Kosu's development and what lies ahead in the coming months, but expect less major development updates and breaking changes for Kosu as it has essentially reached feature-completion, and as we shift our short-term focus to building and shipping Zaidan.
Track the Kosu (test) network live statistics on our hosted web-explorer. Metamask or other web3 browser required.
Thanks for reading, and be sure to check back in for more development, community, and research updates.
Henry Harder
CTO, Paradigm Labs
[email protected]
For more updates like this, follow us on Reddit, Twitter, Medium, and join our community chat server.
All code related to Kosu discussed in this post can be found in the Kosu monorepo on GitHub.
The Zaidan dealer system is proprietary at this time, but there is an open-source client available on GitHub.
submitted by squath to ParadigmMarket [link] [comments]

Development Update (October): Company announcements, feature-complete client, protocol enhancements, Zaidan, and more.

Hello /ParadigmFoundation!
If you haven't already, read about our recent announcements here.
Thanks for reading out latest update. October was another busy month for the Kosu team, with several important milestones reached, including the release of the first feature-complete Go Kosu version.
Additionally, this update marks the first time we will discuss our recently announced request-for-quotation (RFQ) trading system built on 0x, Zaidan. All future development updates will include topics from both Kosu and Zaidan, rather than just Kosu.
Be sure to checkout other recent updates on our old subreddit for a more complete picture of our recent progress.
Note: we will soon move to /ParadigmMarket.

Highlights

Feature completion of Kosu network client

As mentioned in September's update, we did indeed release Go Kosu v0.4 in early October. This release marked the first feature-complete version of the network client, fully implementing the network described in the Kosu whitepaper.
The primary feature introduced in the v0.4 release that pushed kosud to feature completion was the Kosu "order book:" a fixed-size (yet parameterizable) first-in-first-out stack of recent orders kept in-state. Without this feature, the only way to interact with the Kosu order book was to subscribe to order transactions and maintain your own, or dig through the blockchain and "manually" decode historical orders.
Now, any full node or light client can provide the Kosu JSONRPC, now with the latestOrders endpoint, providing a way to page through recent orders and bootstrap a local order book. This feature is especially important for future Kosu light-clients (see last development update) who otherwise would have difficulty bootstrapping an order book.
Implementation of this feature did not occur without incident, and presented an interesting learning opportunity for us. The addition of such a dynamically changing data structure presents challenges when tasked with storing the orders within the Kosu application state trie (ultimately a merkle tree under the hood). Our initial implementation introduced in v0.4 performed fine during generation of the blockchain (normal block processing), but put intense strain on the host machine during syncing of nodes, and in providing the JSONRPC to clients. This issue was addressed with a new CosmosSDK-based list implementation we merged in last week, prior to releasing v0.5 which is now considered to be stable. Read more about this issue and our steps to solve it in the next section.

Investigating and solving a performance issue

As mentioned above, we spent a significant amount of time last month investigating (and ultimately solving) an issue with our order set implementation that was quite difficult to isolate. Ultimately, the issue was with the initial interface and implementation of this order "list" which was highly inefficient under load, and even led to process termination in full nodes when serving the JSONRPC under certain conditions.
We first noticed the issue the morning after we tagged v0.4 and had begun to run the new client version on our internal geographically distributed Kosu test network. We noticed the first symptom after the new v0.4 chain had been running for about a day with only validator nodes. When we tried to sync a new full node with the network, the full node was almost instantly put under intense load (>98% CPU load) as well as the other validators in the network. This led to a temporary halt in new-block production, and the inability for us to sync full nodes.
After restarting the network, this time starting a full node alongside the validators, we noticed the full node was able to keep in-sync with the chain, seemingly without errors. Confused, and tempted to blame Tendermint (which has introduced issues in new version in the past) we enabled the full-node's RPC server and set up a monitoring server to track CPU load, memory usage, file descriptor usage, and other metrics. After turning on some of our peripheral services that consume the Kosu JSONRPC, we noticed that the full node would crash after a period of time (6-12 hours) serving the JSONRPC, with a panic related to the number of open file descriptors (limited to 1024 on most modern systems by default). This was our first major clue. Confirmed by our monitoring dashboard, the full-node serving the JSONRPC would have a suspiciously high open file descriptor count compared to the validators that were not serving the JSONRPC. This indicated either a gross implementation inefficiency or some resource leak.
At this point, and after doing more local testing, Gus, our primary Golang engineer suspected the issue may be with the new order list implementation. He then quickly introduced a new implementation using packages provided by the Cosmos SDK team. After deploying a development build with the new change to the internal test network, we were unable to re-create the issue and deemed it solved, subsequently releasing Go Kosu v0.5. We consider this latest version to be stable, and it has been powering our internal test-network (kosu-wormhole-14) for >400,000 blocks at time of publication. View the latest network stats here (MetaMask required, and select Ropsten network).

Overview of upcoming protocol enhancements

As Kosu stabilizes and gets closer and closer to being ready for public scrutiny and testing, we're excited to announce we will be making a set of changes to some core pieces of staking and key management logic to Kosu, prior to a public announcement.
These changes are focused on providing increased ability for validators to optimize their security configurations, by allowing distinct keys for consensus and application-level messages (incl. support for remote signers and HSMs), the ability to authorize limited-access "proxy accounts" to commit and reveal votes on behalf of stakeholders, as well as a change to the logic used to calculate a validators vote power on the Tendermint network.
Expect many more details about these changes over the coming weeks as we formalize their specification and begin necessary implementation changes. We believe that all stakeholders will benefit from these relatively minor changes to the protocol. In particular, we believe validators will be able to provide higher-quality services to the network and other stakeholders by being more confident in their operational setups.
The first of these proposals landed in the kosu-monorepo master branch this week. It adds the ability for users of the Kosu contract system to authorize and de-authorize limited-access proxy accounts that may commit and reveal votes on behalf of the owner. Read more about these changes and their justification in the PR.

Updates for our recently announced project, Zaidan

Be sure to see the Zaidan announcement before reading this section.
This past week, we were excited to announce Zaidan: a non-custodial RFQ trading system built on 0x we have quietly been developing over the past several months. From now on, our development updates will include news from both the Kosu and the Zaidan projects being developed under the umbrella of Paradigm Labs.
Zaidan is developed very much in the same "decentralized trading" ecosystem as Kosu, but it is a very different project that targets different users, and solves a distinct problem. Zaidan is designed to offer a simple, highly competitive single-transaction trading experience for end users, by leveraging ZEIP-18 (a feature of 0x) and an architecture that uses existing centralized exchanges to provide liquidity and competitive pricing for end users.
While Zaidan is fully non-custodial, in that it uses 0x's on-chain settlement logic to facilitate the transfer of assets between traders, it does require a single central operator (for now). We plan to generalize the Zaidan model over the coming months, with the end goal of creating a dealer-based RFQ trading network (similar in some ways to the construction of NASDAQ) for Ethereum-based assets.
Last month, we pushed our "v1" Zaidan dealer system to feature-completion, and this month are opening it up to the public for a limited beta of the REST API and the web interface (see instructions in the announcement).
Unlike Kosu, the initial Zaidan dealer is a proprietary system, and is being developed in a private repository. However, the TypeScript client library is open-source. Be sure to stay tuned for more announcements and information about Zaidan over the coming weeks and months.
Thanks for reading, and be sure to check back in for more development, community, and research updates.
Henry Harder
CTO, Paradigm Labs
[email protected]
For more updates like this, follow us on Reddit, Twitter, Medium, and join our community chat server.
All code related to Kosu discussed in this post can be found in the Kosu monorepo on GitHub.
The Zaidan dealer system is proprietary at this time, but there is an open-source client available on GitHub.
submitted by squath to ParadigmFoundation [link] [comments]

Continuous Pool Disconnection & 0 Mh/s Speeds

What's up internet/fellow miners. About a week ago I've made the decision to turn my gaming PC to a mining rig. I've had some success solo mining with nicehashminer (Bitcoin miner) but decided that it would be better to mine Ethereum. I've followed the guide and kept coming across these issues. . . I don't know if it's because my config files are whack or another underlying issue.
(EDIT) Connected to us1.ethermine.org:4444 now i'm getting different issues. Here are my most recent logs.
11:11:21:867 c20 args: -epool us1.ethermine.org:4444 -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x 11:11:21:869 c20 11:11:21:878 c20 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 11:11:21:883 c20 º Claymore's Dual GPU Miner - v14.7 º 11:11:21:894 c20 º ETH + DCSIA/LBC/PASC/BLAKE2S/KECCAK º 11:11:21:896 c20 º Supercharged Edition º 11:11:21:899 c20 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 11:11:21:912 c20 11:11:21:914 c20 b745 11:11:22:117 c20 ETH: 2 pools are specified 11:11:22:125 c20 Main Ethereum pool is us1.ethermine.org:4444 11:11:22:128 c20 DCR: 0 pool is specified 11:11:22:200 c20 OpenCL platform: NVIDIA CUDA 11:11:22:201 c20 AMD OpenCL platform not found 11:11:22:441 c20 CUDA initializing...
11:11:22:442 c20 NVIDIA Cards available: 1 11:11:22:443 c20 CUDA Driver Version/Runtime Version: 10.2/8.0 11:11:22:444 c20 GPU #0: GeForce GTX 960, 4096 MB available, 8 compute units, capability: 5.2 (pci bus 1:0:0) 11:11:22:445 c20 Total cards: 1 11:11:26:468 c20 NVML version: 10.430.86 11:11:27:273 c20 SSL: Imported 60 certificates from local storage 11:11:27:308 33f8 ETH: Stratum - connecting to 'us1.ethermine.org' <172.65.218.238> port 4444 (unsecure) 11:11:27:331 33f8 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer", "x"], "id": 2, "method": "eth_submitLogin"}
11:11:27:332 33f8 ETH: Stratum - Connected (us1.ethermine.org:4444) (unsecure) 11:11:27:375 c20 No pool specified for Decred! Ethereum-only mining mode is enabled
11:11:27:383 c20 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
11:11:27:385 c20 ETH: eth-proxy stratum mode 11:11:27:386 c20 Watchdog enabled 11:11:27:388 c20 Remote management (READ-ONLY MODE) is enabled on port 3333 11:11:27:397 c20
11:11:27:404 33f8 buf: {"id":2,"jsonrpc":"2.0","result":true}
11:11:27:405 33f8 ETH: Authorized 11:11:27:412 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:27:468 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa4dc2ea0667952442926fb027314fd0cd783cb300063809c3ce279d84884953f","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:27:505 1cf8 Setting DAG epoch #275... 11:11:29:851 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xb34311e461aeedbc6e19ff26eb477bb24241f67c6fcca04ae0ce5c9ea9416c9b","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:29:852 33f8 ETH: 07/30/19-11:11:29 - New job from us1.ethermine.org:4444 11:11:29:853 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:29:855 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:29:856 33f8 ETH: GPU0 0.000 Mh/s 11:11:30:189 1cf8 Setting DAG epoch #275 for GPU0 11:11:30:192 1cf8 Create GPU buffer for GPU0 11:11:33:056 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x246dfc2d4c7299214c5bff6890eaec46e95326f10a0f7778a2c3711893fc20eb","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:058 33f8 ETH: 07/30/19-11:11:33 - New job from us1.ethermine.org:4444 11:11:33:060 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:067 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:070 33f8 ETH: GPU0 0.000 Mh/s 11:11:33:114 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xffd191ec99473ea193905f976655434dc56a0818a92e0bc3f49759df4ce6a428","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:116 33f8 ETH: 07/30/19-11:11:33 - New job from us1.ethermine.org:4444 11:11:33:118 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:125 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:128 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:182 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:37:184 33f8 ETH: 07/30/19-11:11:37 - New job from us1.ethermine.org:4444 11:11:37:186 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:37:193 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:37:259 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:472 33f8 ETH: checking pool connection... 11:11:37:474 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:37:515 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:214 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x08148d13c03fc8be24926cf555957aa73eebaa6fb9a0f7bc802f2e4a59b27508","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:216 33f8 ETH: 07/30/19-11:11:41 - New job from us1.ethermine.org:4444 11:11:41:218 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:41:225 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:41:247 33f8 ETH: GPU0 0.000 Mh/s 11:11:45:196 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:45:198 33f8 ETH: 07/30/19-11:11:45 - New job from us1.ethermine.org:4444 11:11:45:200 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:45:208 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:45:211 33f8 ETH: GPU0 0.000 Mh/s 11:11:47:486 33f8 ETH: checking pool connection... 11:11:47:488 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:47:529 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:322 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x126f150e00540173459de4712848eeb5993cf40f015de6bef8e1b921b0ab1014","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:324 33f8 ETH: 07/30/19-11:11:49 - New job from us1.ethermine.org:4444 11:11:49:326 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:334 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:337 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:676 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x998033b4ddf28107f5b4d5e55b2d4cdf1ca5206ad5d1b0eacbf4a4a33e04c796","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:677 33f8 ETH: 07/30/19-11:11:49 - New job from us1.ethermine.org:4444 11:11:49:678 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:682 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:684 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:794 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xc29af38a326413d6ccee7806a33d6af54eb6118d2035c9f5e1e042cf355d61fa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:796 33f8 ETH: 07/30/19-11:11:49 - New job from us1.ethermine.org:4444 11:11:49:798 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:805 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:983 33f8 ETH: GPU0 0.000 Mh/s 11:11:51:336 1cf8 GPU0 DAG creation time - 20882 ms 11:11:51:339 1cf8 Setting DAG epoch #275 for GPU0 done 11:11:52:152 2664 GPU0 t=48C fan=45% P=45W 11:11:52:162 2664 Total GPUs power consumption: 45 Watts 11:11:52:404 3344 em hbt: 0, fm hbt: 78, 11:11:52:406 3344 watchdog - thread 0 (gpu0), hb time 1063 11:11:52:407 3344 watchdog - thread 1 (gpu0), hb time 1063 11:11:53:742 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:53:744 33f8 ETH: 07/30/19-11:11:53 - New job from us1.ethermine.org:4444 11:11:53:746 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:53:753 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:55:069 33f8 ETH: GPU0 0.000 Mh/s 11:11:55:350 1cf8 GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:353 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:55:361 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:11:55:363 1cf8 GPU 0, GpuMiner kx failed 1 11:11:55:369 1cf8 Set global fail flag, failed GPU0 11:11:55:410 1cf8 GPU 0 failed 11:11:55:424 37fc GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:432 37fc GPU 0, GpuMiner kx failed 1 11:11:55:436 37fc Set global fail flag, failed GPU0 11:11:55:440 37fc GPU 0 failed 11:11:57:502 33f8 ETH: checking pool connection... 11:11:57:504 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:57:542 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:660 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x787a852f5ac545481815d71276fd0a24414e57d78626b67cb3cb9ba02cf4d0aa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:662 33f8 ETH: 07/30/19-11:11:57 - New job from us1.ethermine.org:4444 11:11:57:664 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:57:672 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:57:675 33f8 ETH: GPU0 0.000 Mh/s 11:11:58:418 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:58:429 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:00:381 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xd9a845fe323638bbfc0901441a5959e6f2e73b625dda369cc55a51d855896e03","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:382 33f8 ETH: 07/30/19-11:12:00 - New job from us1.ethermine.org:4444 11:12:00:383 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:388 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:391 33f8 ETH: GPU0 0.000 Mh/s 11:12:00:490 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x4302100500931a1c914b488a598d8737ff3edbf3f3633468314d6c4e28dab922","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:491 33f8 ETH: 07/30/19-11:12:00 - New job from us1.ethermine.org:4444 11:12:00:492 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:497 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:498 33f8 ETH: GPU0 0.000 Mh/s 11:12:01:488 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:01:500 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:04:502 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:04:504 33f8 ETH: 07/30/19-11:12:04 - New job from us1.ethermine.org:4444 11:12:04:506 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:04:514 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:04:518 33f8 ETH: GPU0 0.000 Mh/s 11:12:04:557 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:04:569 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:07:486 33f8 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000b5f052d5"]}
11:12:07:518 33f8 ETH: checking pool connection... 11:12:07:519 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:07:525 33f8 buf: {"id":6,"jsonrpc":"2.0","result":true}
11:12:07:558 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:07:626 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:07:638 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:08:620 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x25869655f7de1b4af101faf41f51e59fa600e7fea8b139c90dbcfaa55b6c9fb6","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:08:622 33f8 ETH: 07/30/19-11:12:08 - New job from us1.ethermine.org:4444 11:12:08:624 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:08:634 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:08:637 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:592 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x31c0d6df2259de2b9db8cecd3ae97eadb63342697df59490297136aa71c2ac8d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:594 33f8 ETH: 07/30/19-11:12:10 - New job from us1.ethermine.org:4444 11:12:10:596 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:604 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:607 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:696 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:10:706 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:10:768 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x428bacd8f4c294dccc3870b0402b8ea1ba9a5b578ef42309a312ea78e37e7ae4","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:769 33f8 ETH: 07/30/19-11:12:10 - New job from us1.ethermine.org:4444 11:12:10:770 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:775 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:777 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:654 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xf9a5e3322470de0aca5def6fbfa5c559e350f580687ec91f6c452e693b64084e","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:656 33f8 ETH: 07/30/19-11:12:11 - New job from us1.ethermine.org:4444 11:12:11:658 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:676 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:679 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:754 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x77acbeb5ef7ac259f42365da8bc180d934d14d7e61514475e431a74bb33092e8","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:755 33f8 ETH: 07/30/19-11:12:11 - New job from us1.ethermine.org:4444 11:12:11:756 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:761 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:763 33f8 ETH: GPU0 0.000 Mh/s 11:12:13:764 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:13:767 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:15:902 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:15:904 33f8 ETH: 07/30/19-11:12:15 - New job from us1.ethermine.org:4444 11:12:15:906 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:15:914 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:15:917 33f8 ETH: GPU0 0.000 Mh/s 11:12:16:823 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:16:835 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:17:534 33f8 ETH: checking pool connection... 11:12:17:536 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:17:575 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:862 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xac10bfccd03a5ada731630cbccba3733cfbccfecc5b9f531c6373ccd47cf9e71","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:864 33f8 ETH: 07/30/19-11:12:19 - New job from us1.ethermine.org:4444 11:12:19:866 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:19:873 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:19:876 33f8 ETH: GPU0 0.000 Mh/s 11:12:19:893 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:19:903 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:22:679 3344 em hbt: 0, fm hbt: 63, 11:12:22:680 3344 watchdog - thread 0 (gpu0), hb time 31344 11:12:22:682 3344 watchdog - thread 1 (gpu0), hb time 27281 11:12:22:684 3344 WATCHDOG: GPU error, you need to restart miner :( 11:12:22:759 11f8 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:22:770 11f8 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:24:035 3344 Restarting OK, exit...
Config File.txt -

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

WARNING! Miner loads options from this file only if there are not any options in the command line!

-epool us1.ethermine.org:4444 -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x

-dpool stratum+tcp://yiimp.ccminer.org:4252

-dwal DsUt9QagrYLvSkJHXCvhfiZHKafVtzd7Sq4

-dpsw x

-esm 1 -mode 0 -tt 70 -asm 0
epool file.txt-

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorker, PSW: x, ESM: 0, ALLPOOLS: 0

POOL: us1.ethermine.org:4444, WALLET: 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer, PSW: x, ESM: 1, ALLPOOLS: 0

POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1, ESTALE: 1

POOL: us-east1.ethereum.miningpoolhub.com:20535, WALLET: YourLogin.YourWorkerName, PSW: YourWorkerPass, WORKER: YourLogin.YourWorkerName, ESM: 2

ANY HELP/GUIDANCE IS APPRECIATED
submitted by FlawlessPig to EtherMining [link] [comments]

Development Update (October): Company announcements, feature-complete client, protocol enhancements, Zaidan, and more.

Hello /ParadigmMarket (formerly /ParadigmFoundation).
If you haven't already, read about our recent announcements here.
Thanks for reading out latest update. October was another busy month for the Kosu team, with several important milestones reached, including the release of the first feature-complete Go Kosu version.
Additionally, this update marks the first time we will discuss our recently announced request-for-quotation (RFQ) trading system built on 0x, Zaidan. All future development updates will include topics from both Kosu and Zaidan, rather than just Kosu.
Be sure to checkout other recent updates on our old subreddit for a more complete picture of our recent progress.
Note: have just moved to /ParadigmMarket. Our old updates can be found on /ParadigmFoundation.

Highlights

Feature completion of Kosu network client

As mentioned in September's update, we did indeed release Go Kosu v0.4 in early October. This release marked the first feature-complete version of the network client, fully implementing the network described in the Kosu whitepaper.
The primary feature introduced in the v0.4 release that pushed kosud to feature completion was the Kosu "order book:" a fixed-size (yet parameterizable) first-in-first-out stack of recent orders kept in-state. Without this feature, the only way to interact with the Kosu order book was to subscribe to order transactions and maintain your own, or dig through the blockchain and "manually" decode historical orders.
Now, any full node or light client can provide the Kosu JSONRPC, now with the latestOrders endpoint, providing a way to page through recent orders and bootstrap a local order book. This feature is especially important for future Kosu light-clients (see last development update) who otherwise would have difficulty bootstrapping an order book.
Implementation of this feature did not occur without incident, and presented an interesting learning opportunity for us. The addition of such a dynamically changing data structure presents challenges when tasked with storing the orders within the Kosu application state trie (ultimately a merkle tree under the hood). Our initial implementation introduced in v0.4 performed fine during generation of the blockchain (normal block processing), but put intense strain on the host machine during syncing of nodes, and in providing the JSONRPC to clients. This issue was addressed with a new CosmosSDK-based list implementation we merged in last week, prior to releasing v0.5 which is now considered to be stable. Read more about this issue and our steps to solve it in the next section.

Investigating and solving a performance issue

As mentioned above, we spent a significant amount of time last month investigating (and ultimately solving) an issue with our order set implementation that was quite difficult to isolate. Ultimately, the issue was with the initial interface and implementation of this order "list" which was highly inefficient under load, and even led to process termination in full nodes when serving the JSONRPC under certain conditions.
We first noticed the issue the morning after we tagged v0.4 and had begun to run the new client version on our internal geographically distributed Kosu test network. We noticed the first symptom after the new v0.4 chain had been running for about a day with only validator nodes. When we tried to sync a new full node with the network, the full node was almost instantly put under intense load (>98% CPU load) as well as the other validators in the network. This led to a temporary halt in new-block production, and the inability for us to sync full nodes.
After restarting the network, this time starting a full node alongside the validators, we noticed the full node was able to keep in-sync with the chain, seemingly without errors. Confused, and tempted to blame Tendermint (which has introduced issues in new version in the past) we enabled the full-node's RPC server and set up a monitoring server to track CPU load, memory usage, file descriptor usage, and other metrics. After turning on some of our peripheral services that consume the Kosu JSONRPC, we noticed that the full node would crash after a period of time (6-12 hours) serving the JSONRPC, with a panic related to the number of open file descriptors (limited to 1024 on most modern systems by default). This was our first major clue. Confirmed by our monitoring dashboard, the full-node serving the JSONRPC would have a suspiciously high open file descriptor count compared to the validators that were not serving the JSONRPC. This indicated either a gross implementation inefficiency or some resource leak.
At this point, and after doing more local testing, Gus, our primary Golang engineer suspected the issue may be with the new order list implementation. He then quickly introduced a new implementation using packages provided by the Cosmos SDK team. After deploying a development build with the new change to the internal test network, we were unable to re-create the issue and deemed it solved, subsequently releasing Go Kosu v0.5. We consider this latest version to be stable, and it has been powering our internal test-network (kosu-wormhole-14) for >400,000 blocks at time of publication. View the latest network stats here (MetaMask required, and select Ropsten network).

Overview of upcoming protocol enhancements

As Kosu stabilizes and gets closer and closer to being ready for public scrutiny and testing, we're excited to announce we will be making a set of changes to some core pieces of staking and key management logic to Kosu, prior to a public announcement.
These changes are focused on providing increased ability for validators to optimize their security configurations, by allowing distinct keys for consensus and application-level messages (incl. support for remote signers and HSMs), the ability to authorize limited-access "proxy accounts" to commit and reveal votes on behalf of stakeholders, as well as a change to the logic used to calculate a validators vote power on the Tendermint network.
Expect many more details about these changes over the coming weeks as we formalize their specification and begin necessary implementation changes. We believe that all stakeholders will benefit from these relatively minor changes to the protocol. In particular, we believe validators will be able to provide higher-quality services to the network and other stakeholders by being more confident in their operational setups.
The first of these proposals landed in the kosu-monorepo master branch this week. It adds the ability for users of the Kosu contract system to authorize and de-authorize limited-access proxy accounts that may commit and reveal votes on behalf of the owner. Read more about these changes and their justification in the PR.

Updates for our recently announced project, Zaidan

Be sure to see the Zaidan announcement before reading this section.
This past week, we were excited to announce Zaidan: a non-custodial RFQ trading system built on 0x we have quietly been developing over the past several months. From now on, our development updates will include news from both the Kosu and the Zaidan projects being developed under the umbrella of Paradigm Labs.
Zaidan is developed very much in the same "decentralized trading" ecosystem as Kosu, but it is a very different project that targets different users, and solves a distinct problem. Zaidan is designed to offer a simple, highly competitive single-transaction trading experience for end users, by leveraging ZEIP-18 (a feature of 0x) and an architecture that uses existing centralized exchanges to provide liquidity and competitive pricing for end users.
While Zaidan is fully non-custodial, in that it uses 0x's on-chain settlement logic to facilitate the transfer of assets between traders, it does require a single central operator (for now). We plan to generalize the Zaidan model over the coming months, with the end goal of creating a dealer-based RFQ trading network (similar in some ways to the construction of NASDAQ) for Ethereum-based assets.
Last month, we pushed our "v1" Zaidan dealer system to feature-completion, and this month are opening it up to the public for a limited beta of the REST API and the web interface (see instructions in the announcement).
Unlike Kosu, the initial Zaidan dealer is a proprietary system, and is being developed in a private repository. However, the TypeScript client library is open-source. Be sure to stay tuned for more announcements and information about Zaidan over the coming weeks and months.
Thanks for reading, and be sure to check back in for more development, community, and research updates.
Henry Harder
CTO, Paradigm Labs
[email protected]
For more updates like this, follow us on Reddit, Twitter, Medium, and join our community chat server.
All code related to Kosu discussed in this post can be found in the Kosu monorepo on GitHub.
The Zaidan dealer system is proprietary at this time, but there is an open-source client available on GitHub.
submitted by squath to ParadigmMarket [link] [comments]

Ethereum private key with all zeroes leads to an account with 5000$ on it

The private key 0000000000000000000000000000000000000000000000000000000000000000 generates the address 0x3f17f1962B36e491b30A40b2405849e597Ba5FB5, which has 10 ethereums on it. See https://etherscan.io/address/0x3f17f1962B36e491b30A40b2405849e597Ba5FB5 and https://ethdir.io/ first page . However, when I try to import it or sign a transaction with it, the network refuses to take the raw tx. How is it possible that people can send ethereums to that address yet it is virtually unreachable on the network?
The error message is "Error! Unable to broadcast Tx : {"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"invalid sender"}}".
submitted by laci420 to CryptoTechnology [link] [comments]

Adding good peers to ethereum node using etherscan

My ethereum node was having very less number of peers, an hence syncing was slow. Etherscan provides a list of enode urls but I required something to copy all the enodes and add them to my peer list of Ethereum. So I created a script which runs on etherscan node explorer page https://etherscan.io/nodetrackenodes in browser console and gets all enode URLs.

These URLs are converted to commands which can be pasted in server console directly to add them as peers. The script used is given below
var enodeTable = document.getElementsByClassName("table")[0] var enodeList = [] var info = [] var commandList = [] var commandStart = 'curl --data \'{"jsonrpc":"2.0","method":"parity_addReservedPeer","params":["'; var commandEnd = '"],"id":0}\' -H "Content-Type: application/json" -X POST localhost:8545' for (i = 1; i < enodeTable.rows.length; i++) { var enodeUrl = ""; var command= ""; // GET THE CELLS COLLECTION OF THE CURRENT ROW. var objCells = enodeTable.rows.item(i).cells; var btn = objCells[8] copySpan = btn.getElementsByClassName("d-none") enodeUrl = copySpan[0].innerText enodeList.push(enodeUrl); command = commandStart + enodeUrl + commandEnd; commandList.push(command); } var arrLength = commandList.length for(i=0; i< arrLength; i++) { console.log(commandList[i]); } 
submitted by ayushyachitransh to ethereum [link] [comments]

QuarkChain Bi-weekly Project Progress Report: June 28 — July 11, 2019

QuarkChain Bi-weekly Project Progress Report: June 28 — July 11, 2019

https://preview.redd.it/930o2j7jax931.png?width=900&format=png&auto=webp&s=55580b597fb35c15493d5498069429dd4dcd1716
Welcome to the 35th QuarkChain Bi-weekly Report for the period from June 28 to July 11. For the past two weeks, we announced plenty of news and attended many events.

Highlights:

  • QuarkChain mainnet officially opens transaction function;
  • QuarkChain burned 40% (4 Billion) ERC20 tokens and converted them into mainnet mining rewards.
  • Guardian Plan Update: Term I has been finished, and the corresponding rewards have been released. The second term of Aegis Guardians and Elf Guardians are performing the duties.
  • QKC was listed on PIEXGO, which opened QKC/USDT, QKC/BTC trading. Meanwhile, UDAP was officially listed on PIEXGO and became the first IXO project in QuarkChain’s eco-partnership layout.
  • QuarkChain together with 47 companies and organizations joined in Binance’s Charity to unveil a stable coin for the alleviation of period poverty.
  • The QuarkChain team actively participated in online and offline activities. They discuss how the blockchain ecosystem can apply in all walks of life, and the general trend of the blockchain industry with people from various trades and industries.

1. QuarkChain News

Development Progresses
# Major Updates
## Added
  • Supported the function to enforce minimum gas price for accepting transactions and mining block inclusion
  • Supported the function of discarding under-priced transactions when the transaction queue is full
  • Added a new function of turning on/off public and private JSONRPC servers in the configuration
  • Implemented database integrity check tooling to make sure the consensus algorithm will not break after new code changes by replaying the whole blockchain history
  • Added utility scripts for coinbase and balance-related calculations
  • Implemented the function of showing the whole transaction history in any shard
  • Supported turning on profiling mode for measuring cluster performances
  • Added a token ID parameter to ‘gasPrice’ JSONRPC endpoint
## Updated
  • Improved block processing performance during synchronization and blockchain history replay, where the time usage of replaying the whole history dropped from 1 day to 1 hour
  • Simplified cross-shard transaction processing with more testing scenarios
  • Improved transaction history lookup function by normalizing addresses in the same full shard ID
## Fixed
  • Fixed cross-shard transaction gas consumption calculation for root chain coinbase rewards
QuarkChain mainnet officially opens transaction function
In accordance with the consensus and roadmap, we are pleased to announce that QuarkChain mainnet now officially opens the transaction function. We welcome community members to use it and experience the smooth transaction brought by the QuarkChain sharding technology.
For more details, please click HERE.
QuarkChain burned 40% (4 Billion) ERC20 tokens
According to the original token distribution plan, 4 billion tokens will be awarded to miners as total mining rewards. In order to convert these tokens into mainnet mining rewards, QuarkChain burned these tokens in the ERC20 contract and converted them into mainnet mining rewards.
For more details, please click HERE.
QuarkChain Guardian Plan Term I Ended and Term II Election Result Was Announced
As Term I guardian plan ended, QuarkChain already sent the corresponding rewards to the guardians and to the voters at the promised rebate ratio. Meantime, the second term of the Guardian Plan poll ended. Members can check the election result. Considering that staking restricts the users to participate in other activities, we decided to postpone the launch of the third term of the Guardian Plan, and will restart it at a better time.
For more details, please click HERE.

2. Partnerships

QKC Was Listed on PIEXGO
PIEXGO officially listed QKC on July 1, 2019, which opened QKC/USDT, QKC/BTC trading. Top 20 winners in the QKC trading competition were announced. Thank everyone for the enthusiastic participation in the QKC trading competition. The rewards will be issued within 7 working days after the list announced.
For more details, please click: https://piexgo.zendesk.com/hc/en-us/articles/360030650991-Top-20-Winners-of-QKC-Trading-Competition-Announced
UDAP Launched on PIEXGO doing IXO and Became the First Project Using QKC to Do the Fundraising
UDAP was officially listed on PIEXGO and became the first IXO project in QuarkChain’s eco-partnership layout. QuarkChain’s secure, flexible and high throughput underlying technology, coupled with UDAP’s role that links various application layers, will enable the measurement and connection of various virtual and physical assets, and ultimately achieve wide commercial applications.
For more details, please click HERE.
QuarkChain participated in Binance’s charity event and promoted global women’s health with “Pink Coin”
July 3, 2019 — Binance Charity Foundation announced the first strategic alliance of 46 companies and organizations as founding partners to introduce ‘Pink Care Token’ (PCAT). Dr. Qi Zhou-QuarkChain’s founder and CEO said: “This 46-agency alliance event is a grand philanthropy with different strengths. QuarkChain’s flexibility is compatible and inclusive. We are willing to provide technical assistance within our capabilities for the release of the Pink Care Token to create more well-being for women around the world.”
For more details, please click HERE.
Partnership with Rebit AI

https://preview.redd.it/prph3jmqax931.png?width=1218&format=png&auto=webp&s=466adee10a3d49b13899b3c54ab714faf833c447
REBIT AI is a company that has been a 15-year solution partner to Samsung Electronics which provided embedded keyboard solutions to some of Samsung’s Galaxy series. With this technology, REBIT AI is prepared a crypto rewarding keyboard DApp.
Through the partnership with Samsung Electronics REBIT AI’s keyboard has finished testing for all languages, which makes it one of the only 4 keyboard applications that can provide such language coverage in the world. It will provide AI-based word completion and suggestion as Galaxy smartphone keyboards do. Furthermore, the DApp will utilize AI-based big data analytics and recommendation technology, which has been developed with Samsung Electronics but not used in its phones, for AD targeting and big data services. REBIT AI has already created a business model based on its big data competencies and is in steps of advancing it.
As such, top Korean companies like KT(Telecom), ActozSoft, Netmarble, global Ad platform YeahMobi, and MotherBrain have already partnered with REBIT AI and is currently expanding its partnerships also into India and Japan.
REBIT AI CEO Donjun Shin is upset about seeing the low utilization of unstructured big data and therefore has great expectations for its crypto rewarding keyboard business.
We are very happy to have REBIT AI as a member of QuarkChain Ecosystem

3. Marketing Events and Activities

6/27 Consensus, On-Chain Governance and Economic Models in the World of Blockchain in San Francisco
Around 100 delegates joined the event of Consensus, On-Chain Governance and Economic Models in the World of Blockchain. Industry experts and leaders from investment, finance, blockchain presented and participated in keynote and various panel discussions. With the theme, “Consensus, On-Chain Governance and Economic Models in the World of Blockchain”, this event explored several key topics relating to consensus, on-chain governance and economic models from technology and investment perspective.
6/28 Chongqing Liangjiang New Area Event in Silicon Valley

https://preview.redd.it/b8vl2zhpax931.png?width=1212&format=png&auto=webp&s=bfdad42939651ec4027697cef664ef38953c10b6
Chongqing Liangjiang New Area Investment Delegation visited the United States in June. The event was held in Silicon Valley Science and Technology Innovation Center on June 28. QuarkChain was invited to participate in the event as an outstanding start-up enterprise in Silicon Valley. The leaders of Chongqing Liangjiang New Area had a deep discussion on QuarkChain’s enterprise solution. The director highly praised QuarkChain’s technology development and will continue in-depth cooperation with QuarkChain in the future.
6/29 The Ethereum Technology & Application Convention

https://preview.redd.it/kvayo8qxcx931.png?width=1144&format=png&auto=webp&s=e4f96fdaaf22497b91ccc5d907c997fe2faa515e
The Ethereum Technology & Application Convention organized by CSDN, Linktime was held on June 29–30 in Beijing. QuarkChain engineer Ping Ke was invited to participate in the event. They discussed Ethereum 2.0, blockchain tech with Vitalik Buterin and other industry leaders. During the event, Ping Ke introduced QuarkChain’s state sharding technology to offer a better solution to blockchain trilemma. Vitalik Buterin said using sharding technology is his next step.
6/29 GCDC2019 GOS Chain Eco-application Developers Conference

https://preview.redd.it/0qx18qb4dx931.png?width=1174&format=png&auto=webp&s=bb77056c9135552fd2715e3b59fe6727fb2e0e37
GOS Chain Eco-application Developers Conference was held in Hangzhou on June 29. The conference invited famous scholars, developers, and scientists to show the frontier public chain technology of GOS Chain to developers, industry partners and enterprises from all over the country. During the conference, attendees explained the direction of investment development and discussed the ecological application of the blockchain. QuarkChain scientist Dr. Yaodong Yang was invited to attend the event and he delivered a keynote speech entitled “Shards and Flexibility of Blockchain”.
7/4 QuarkChain Founder and CEO Dr. Zhou Joined Online Discussion about Libra
On July 4, Dr. Qi Zhou — QuarkChain CEO and founder attended BibiNews’ sharing session and explored Libra’s opportunities and challenges. Dr. Zhou indicated that QuarkChain hopes to work with Libra in the field of public chain technology and learn from each other. Libra wants to implement the blockchain technology for serving 1 billion people, but Libra can’t do it yet, and QuarkChain already has the solutions. In addition, it is worth learning that Libra can work with high-quality business partners and participate in community governance.
7/4 QuarkChain CMO attended “Is Libra the Future of Blockchain” Panel

https://preview.redd.it/cj46uymcdx931.png?width=1206&format=png&auto=webp&s=739eab0ebeef410dba674c342834ca8b839bd5cf
On July 4, QuarkChain co-founder and CMO Anthurine Xiang attended an event that was organized by InVault. In the panel, she discussed views on Libra alongside big institutions such as McDonald, the Chinese Academy of Science Institute, Alipay’s Antfin and Alchemint. The entrance of mainstream traditional institutions brings more users, at the same time, it can also let us learn how mainstream institutions think of the blockchain industry.
7/6 CMO Joined BIGGERCHAIN 2019 China’s blockchain leaders Forum

https://preview.redd.it/a91ogc3edx931.png?width=1270&format=png&auto=webp&s=3a4c6cbf51a5da58e1ea29374f13debbcdf25cc5
At the BIGGERCHAIN 2019 China’s blockchain leaders Forum, held in China on July 6, QuarkChain CMO Anthurine gave an excellent speech about how public blockchain will evolve in the future. Staking also became a topic of discussion. Anthurine discussed the topic of “Benefit & Equity- The Rising of Staking Economic” and commented about the benefits of staking, capital security and how to attract the participators. Anthurine Xiang believes that “Staking” can be understood as pledging. However, staking also has the meaning of stock equity and earnings. Staking emphasizes participation. We encourage people to participate in community ecological development and become part of it, rather than simply gaining benefits by investing tokens in nodes. The meaning of staking is to encourage people to participate in community ecology.

Upcoming Event

Tortoise in China

https://preview.redd.it/5cxu1o3gdx931.png?width=1222&format=png&auto=webp&s=24e615cccdd9a914707bc6c7a60aa85c98c97269
Tortoise in China is a field visiting project which lasts nearly half a year. It includes in-depth interviews with 50 representative people inside and outside the industry and interviews with 100 benchmarking enterprises in the industry. CBO Du Ting, QuarkChain co-founder, will participate in the round table “Application Discussions”. He will share how QuarkChain uses sharding technology to achieve application landing.
7/14 Block Global ECO Summit

https://preview.redd.it/d4cxui5idx931.png?width=1302&format=png&auto=webp&s=0a07b0d25db1425b74354411e4429a6a2652b37a
On July 14, the 2019 Block Global ECO Summit hosted by BLOCK GLOBAL, Block360 and GLOSFER will be held in Shenzhen, China. QuarkChain co-founder and CBO Du Ting, CMO Anthurine will participate in the event. This summit will focus on blockchain technology and application, and discuss how to control the timing before the bull market. Industry experts will share the latest development results of blockchain policy, standards, technology, and application. Ting Du and Anthurine will discuss the industrial ecology and risks of blockchain, and explore the global development trend of blockchain.

4. FYI

There is a QuarkChain’s official Reddit account. We will collect questions before AMA. Please feel free to post questions and suggestions on Reddit. https://www.reddit.com/quarkchainio/comments/cc0m0q/quarkchain_weekly_discussion_ama_0711_7_pm_pst/
Thanks for reading this report. QuarkChain always appreciates your support and company.
Website https://www.quarkchain.io
Telegram https://t.me/quarkchainio
Twitter https://twitter.com/Quark_Chain
Medium https://medium.com/quarkchain-official
Reddit https://www.reddit.com/quarkchainio/
Facebook https://www.facebook.com/quarkchainofficial/
Discord https://discord.me/quarkchain
submitted by QuarkChain to quarkchainio [link] [comments]

QuarkChain Bi-weekly Project Progress Report: May 03 — May 15, 2019

QuarkChain Bi-weekly Project Progress Report: May 03 — May 15, 2019

https://preview.redd.it/e4xwjo1edhy21.png?width=904&format=png&auto=webp&s=75c2a7cf430a3478bed534dc563ae5ac64b0f581
Welcome to the 31st QuarkChain Bi-weekly Report for the period from May 03 to May 15.

1. Development Progresses

# Core Updates
## Major Milestones
- Successfully launched mainnet on April 30, 2019
## Added
- Released the mainnet AWS AMI
- Provided the mining tutorial based on AWS AMI
- Added indexing for minor blocks
- Added JSONRPC endpoint to provide P2P routing table for better debuggability
- Updated outdated JSONRPC documents
- Updated JSONRPC documents to support token swap
## Changed
- Enhanced transaction pools
- Updated mainnet bootstrap nodes’ IP
- Added mainnet bootnode config for qrktool
## Fixed
- Removed unused parameters when adding the root blocks
  1. Partnership

https://preview.redd.it/f8if3nuhdhy21.png?width=1444&format=png&auto=webp&s=2a298e911afb1a5beaedd4d4482e281e4006ed4b
CBNT (Create Breaking News Together) is a decentralized blog platform based on blockchain technology and an ecosystem model of DPGC (Decentralized Professional Generated Content). CBNT has a unique model of “participating is mining” in which writing content, liking and commenting on all counts towards mining. With an internal incentive mechanism, a positive interaction will be forged between authors and viewers, and high-quality content will be generated. At CBNT, due to the unique mining model, a large number of transactions will be recorded on chain, with the goal of being a truly decentralized project. CBNT is eager to find a blockchain with high performance.
The mainstream blockchains, like Ethereum, are not adequate for the needs of CBNT. Limited throughput ability will affect the transaction processing speeds, or even trigger network congestion. This is especially true in high-frequency processing scenarios, like content sharing and social mining. In addition, the high gas fees also stop users’ willingness to interact on the CBNT platform, and thus a new blockchain is needed!
With its high throughput, flexibility, and performance, QuarkChain is qualified to solve the CBNT’s problems. On the QuarkChain network, transactions at any time and place will be completed and confirmed quickly, on the grounds of its sharding technology. As the number of shards increases, the transaction speed will increase in a linear way. The TPS on mainnet is expected to reach 100K+, and the testnet has already achieved a speed of 14,000+ TPS. With QuarkChain’s high throughput network, they give the maximum potential to achieve a decentralized and highly efficient next-generation blog.

3. Event

Consensus NY 2019
Consensus was the one global conference and expo that brought entrepreneurs, intrapreneurs, traders, developers, academics, students and people with curiosity together under one roof to explore, collaborate and debate the future of blockchain and crypto. QuarkChain CMO Anthurine Xiang was invited to attend Block Plus Summit. She moderated a panel discussion: Platform Wars and Privacy Protection in Blockchain. Stephen Tse, founder and CEO of Harmoney, Sandeep Nailwal, COO of Matic Network, Jason Qiao, Chief Ecosystem Officer of PlatOn joined in this panel, and gave their opinions about blockchain platform now and future.
Consensus After Party-Meet QuarkChain, Polkadot and AVA Labs
https://preview.redd.it/kc128oliehy21.png?width=1186&format=png&auto=webp&s=bbeaa96d18ae36b8d04c7e14fda73a74fa37b248
May 13, Anthurine Xiang, CMO of QuarkChain, together with Polkadot and AVA Labs hold an event about public chain and cross chain at Midtown Hilton. During the event, they shared their opinions about public chain and cross chain. Anthurine detailed introduced QuarkChain 2.0: one of the greatest features of QuarkChain 2.0 is flexibility, which extends to being friendly to new technologies and having stronger self-evolution capabilities. That is to say, each shard can have its own consensus mechanism, ledger model, transaction model, and token economics. With this, we can even include existing public chains.
Sharding Technology Panels
https://preview.redd.it/z61yscpgehy21.png?width=1122&format=png&auto=webp&s=1a682c766012a55e2c6a8089b8ae18c932951505
May 14, QuarkChain, together with Harmoney and Thendercore held an event about sharding blockchain technology. ETH 2.0, Kadena, Near Protocol, Zilliqa, and Ontology also presented during this event. We had two panels which focused on sharing updates on the progress of each project. The first panel was Deep Dive into Sharding Technology — Each project’s different approach and progress on sharding and what is to come in 2019. The second panel was Real World and Sharding — Each project’s progress on how to use sharded blockchains to make an impact outside of Cryptosphere. Anthurine, CMO of QuarkChain and Junjia, QuarkChain engineers detailed introduced QuarkChain’s state sharding technology, and a system structure of root chain-shards which can be compatible with various consensus mechanisms. On the basis of high throughput, more than 51% hash power will be protected by root chain, and compatible with decentralized PoW, PoS, and other consensus mechanisms. It puts forward an excellent solution to blockchain trilemma, which is an important contribution to the future development of the industry.

Upcoming Event

Blockchain Week in Hangzhou
This is the first Blockchain Week in Hangzhou. There are three main schedules, namely, ChainNode Technology Open Day on May 16 (morning session) and Friends in Blockchain (afternoon session). Both of them are small-scale but high-end gatherings, with the highest number of entrants at 300. May 17 will be the peak conference of the Global Blockchain (Hangzhou) in 2019. It is expected that the number of participants will reach 1500.

4. QuarkChain in the News

Chain Curation Research: QuarkChain: https://www.thedailychain.com/blog/chain-curation-research-quarkchain/
What Will Happen When Proof-Of-Stake (PoS) Becomes Obsolete? — Quarkchain’s Answer: https://www.investinblockchain.com/what-will-happen-when-proof-of-stake-pos-becomes-obsolete/

FYI

Website https://www.quarkchain.io Discord discord.me/quarkchain Telegram https://t.me/quarkchainio Twitter https://twitter.com/Quark_Chain Medium https://medium.com/quarkchain-official Reddit https://www.reddit.com/quarkchainio/ Facebook https://www.facebook.com/quarkchainofficial/
submitted by QuarkChain to quarkchainio [link] [comments]

Development Update (February): token and staking system updates, new Golang client, and more.

Hello again, /ParadigmFoundation!
Thanks for reading this (slightly-delayed) February development update. It was another busy month at Paradigm, and we're excited to tell you about what has changed since the last update. As always, feel free to comment and ask questions here, or on our chat server.
For an in-depth view of protocol progress, and to be the first to see new updates, be sure to follow the activity on our GitHub. Much of our monthly progress doesn't make it into these updates.

Highlights

Latest protocol core contract system version deployed (on Ropsten)

February was a big month for the internal ParadigmContracts that make up the Ethereum component of the Paradigm protocol.
The latest development version of the system was deployed with a new token and set of staking systems built around DIGM: the native ERC-20 token for the Paradigm protocol.
Included in the latest deployment is the ValidatorRegistry contract, a custom token-curated registry (TCR) that is used to select the validators of the OrderStream network. It allows DIGM holders to vote to select new and curate existing network validators. The registry features simple economic mechanisms to encourage the curation of a high-quality validator set.
There are many exciting features included in this latest deployment, and many more coming in the following weeks. So stay tuned, and check out the source for the latest updates.
Shoot me a message with your Ropsten address for some testnet DIGM if you want to play around with the system (make sure to be on the ropsten network when interacting with the functions at that link).

Preparing for ParadigmCore v0.8

In the last update, we mentioned ParadigmCore v0.8 which will be the first version of the application to support dynamic updates to the active Tendermint validator set based on the ValidatorRegistry Ethereum contract (see above). This version also includes the new JSONRPC/WebSocket API (see below), and additional enhancements.
Development on version 0.8 is currently taking place here, and undergoing final revisions and testing before being merged and marked as a release version.
The OrderStream current test-network deployment is running the latest v0.8 release candidate of ParadigmCore, and is being load-tested for the next few days.

About ParadigmCore's new JSONRPC/WebSocket API

Click here to see the latest documentation for the API discussed in this section, and here for the documentation of the actual server implementation.
In the last update (linked above) we also discussed the new JSONRPC WebSocket API being designed and built for ParadigmCore. JSONRPC (2.0) is a simple remote procedural call (RPC) standard that provides a common format for API requests and response that can be implemented in any language over any transport.
The first version of ParadigmCore's JSONRPC API is affectionately called the StreamAPI, and is available solely over a WebSocket connection (thus JSONRPC/WebSocket). It provides methods for real-time subscriptions to various "events" on the OrderStream, such as new blocks and new orders. The initial implementation also provides more conventional "request/response" methods for performing state queries to local nodes, and submitting orders to the network.
The polling methods (like state.query) will eventually be made available via JSONRPC/HTTP with POST requests, and URI/HTTP to support GET requests.
Check out the (WIP) documentation for the API here, or the initial StreamAPI server implementation here.

0x OrderStream-SRA (and Zaidan) updated for new JSONRPC API

OrderStream-SRA has been patched to work with the latest ParadigmCore API (see above). The hosted version of the software found at sra.zaidan.io/v2/ has been updated as well. Our hosted version of 0x Instant continues to allow access to the OrderStream testnet's aggregated 0x liquidity, and the Instant interface.
For those unfamiliar, OrderStream-SRA is Paradigm's implementation of the HTTP 0x Standard Relayer API (SRA) for the OrderStream network. It allows access to the 0x order messages relayed on the OrderStream in their native format over the SRA compliant interface.
It was built to 1) enable access to the OrderStream via 0x SRA 2) to support 0x instant 3) demonstrate the architectural model of "derived" order books being constructed a layer above the OrderStream relay network itself.
The software currently uses a MongoDB backend, and includes instructions and configuration for use with Docker. A live version of the software is hosted at https://sra.zaidan.io/v2/, and documentation for the HTTP 0x SRA can be found here. Contributions welcome.

Announcing work on Golang reference implementation of the OrderStream

We're excited to announce that work has begun on a Golang client implementation for the OrderStream network, which will serve as the reference implementation of the Paradigm protocol, along with the contract system described above.
It is likely the ParadigmCore name will be given to the Golang client in the future, so to avoid confusion the current OrderStream implementation will be called TS-ParadigmCore in the next development update.
For the initial Go implementation of ParadigmCore, we will not seek cross-client compatibility with the TypeScript version. Instead, we are working on a full specification of the V1 Paradigm protocol which the Go client will be built to meet.
Once complete, the TypeScript implementation will be updated to meet the new protocol specification. Eventually, the goal is to have two OrderStream client implementations that can function on and support the same network. The primary barrier to this being possible in the current implementation is the lack of a clearly specified Merkle tree structure for storing state data, and poorly specified transaction serialization. The upcoming re-specification will guide future implementers, and ensure cross-client compatibility is possible.

Important notice

The OrderStream network is in a test-net phase, and should be treated as beta software. However, there are current main-net (fillable, valid, and collateralized) 0x orders being processed and relayed by the OrderStream test-network.
This means you can execute main-net 0x orders as a taker, using the OS network's maker liquidity. So while all Paradigm protocol contracts exist solely on the Ropsten test-network, some (or many/all) orders being process on the relay network are executable on the Ethereum main-net, with real assets.
Please use all software discussed in this post at your own discretion, and in compliance with local regulations.
Thanks for reading, and be sure to stay tuned for more development and research updates.
Henry Harder
CTO, Paradigm Labs
[email protected]
For more updates like this, follow us on Reddit, Twitter, Medium, and join our community chat server.
All code and software discussed in this post can be viewed on our GitHub.
submitted by squath to ParadigmFoundation [link] [comments]

How tio connect Ethereum Wallet to Parity Node 2.x

I am running a full node parity which is always syncing, and want to connect the official Ethereum GUI wallet it to it, but have not been able to get it working. I have tried RPC over http://localhost port 8545 . I am on Windows and have heard there is an IPC pipe method but am not sure how to do in Windows. I would prefer a secure method over https or pipes. Both are latest versions-
command for wallet: "Ethereum Wallet.exe" --rpc http://localhost:8545
command for parity: parity.exe --mode=active --jsonrpc-apis=all
error I see when wallet trys to connect to parity is "subscriptions are not available on this transport"
...Any help is appreciated.
submitted by techtot to EtherMining [link] [comments]

"Error: base fee exceeds gas limit"

I'm trying to deploy a contract using Truffle and Metamask, but I keep getting this error:
Error: Error: Error: [ethjs-rpc] rpc error with payload {"id":4935577550328,"jsonrpc":"2.0","params":["0xf8d78085012a05f2008256cc8080b884d69e1e2d000000000000000000000000f17f52151ebef6c7334fad080c5704d77216b732000000000000000000000000000000000000000000000000000000000000001673647364000000000000000000000000000000000000000000000000000000007364736400000000000000000000000000000000000000000000000000000000822d46a0a06fb20f486030c26879b18e6bb40a5bf28e1e4a6588ebd5eb6b834e520da624a003c8b5c698af2e6478278c2614b6e7e00b0fe61ccf971b6f2cc29e7c327458be"],"method":"eth_sendRawTransaction"} Error: base fee exceeds gas limit 
I tried following the advice of the last comment here, but it didn't seem to solve the problem.
For reference, I am trying to execute this contract using Truffle:
https://coursetro.com/posts/code/104/Finishing-our-Smart-Contract-and-Using-it-on-Ropsten
Any help would be greatly appreciated!
submitted by Turbulent_Repair to ethdev [link] [comments]

Monthly Project Report in December

Monthly Project Report in December
The process details of project technology
Scry Dapp Bottom Layer Function
  1. Rewrite the interface to GRPC
  2. Deal with different types of conversion in GRPC
  3. Build the quorum test environment and test performance
  4. Install multi-node EOS environment and test performance
  5. Solve the version problem of log printing
  6. Refactor the charge code
  7. The code is transferred to city chain project
  8. Build the lightning network environment and verify
  9. Improve the charge confirmation code
  10. Modify the configuration file usage
  11. Complex JSON data conversion in the configuration file
  12. Modify the dot log method, add log output path selection
  13. GRPC disconnection to reconnect
  14. GRPC interface return to define make (map[string]string) key-value pairs and arrays processing
  15. Rewrite the previous GRPC server, client code (due to key-value pairs and array adjustments)
  16. Analyze the performance bottlenecks, throughput and capacity issues of block-chain
Userself- authentication
  1. Deal with the problem of serialization of parameter fields in JSONRPC
  2. Rewrite the data interaction process in the self-authentication process to JSON-RPC implementation.
  3. Integrate all functions implemented on the server into the self library.
  4. Prepare to add GRPC support
  5. Put the GPRC into a single thread to operate
  6. Organize the authentication process and data structure
  7. In the simulation authentication library process, the authentication related functions are realized in a single thread
  8. Separate the authentication service from the normal business
  9. Solve the problem of data synchro-nization between different threads
  10. Finish the self-authentication document, improve the authentication timing diagram, negotiation process description
Protocol layer
  1. Improve the component interaction se-quence diagram
  2. Design transaction state migration, de-fine notification event
  3. Define the interface between the front end and the contract, design data structure
  4. Modify and improve the business pro-cess of protocol layer and the sequence diagram of component inter-action
  5. Ethereum on-chain operation details: monitor event, scan new blocks, accept trading results, etc.
  6. Write some codes for PoC - code overall framework
  7. Write some codes for PoC - transaction part
  8. Try IPFS on the command line and web interface
  9. Realize IPFS to upload and download (Go) files on the local node
  10. Optimize the realized code, add the timeout processing mechanism
  11. Write some codes for PoC - core module
  12. Write some codes for PoC - util module
  13. Carry out business module coding
  14. Realize IPFS to upload and download the file in p2p network environment
https://preview.redd.it/1lae2nwr6b821.png?width=1107&format=png&auto=webp&s=fc3d14ba0713ff43a04f8563392a8a743b44f967
Cashbox Wallet
  1. Organize the wallet functions that need to be added in the next development step
  2. Add local image support in scanning QR code
  3. Research Android Keystore:
  4. Research the scheme of separating data synchronization from transaction signature
  5. Solve the Chinese garbled code problem in GRPC
  6. Background management - login function to achieve
  7. Background management - integrated vue-quill-editor
  8. Modify test wallet interface problem
  9. Check and confirm that the seed generation function is safe
  10. Draw the prototype of contact infor-mation and language switching interface
  11. Set out rules of restricting interaction methods for password accounts
  12. Realize the switching language function in application
  13. Research the introduction document of checkpoint realization
  14. Background management - wangEditor integration
  15. Background management - solve the problem that directly display base 64 code image
  16. Background management - front-end generate HTML
  17. Background management - optimize the design style of left menu bar, top navigation bar, interface page.
  18. Organize background system require-ments, design database and generate template code
  19. Design announcement interface and modify the front-end layout code
Scry DB
  1. Use UDP to find nodes and use TCP to sync data
  2. View the realization of gossip protocol
  3. Organize the priority order issue of the multi-threaded issue on the implementa-tion process
  4. Use the Tokio library to achieve simul-taneously monitoring multiple addresses
  5. Achieve the task team of JobQuene
  6. Generic extension method
  7. Match the complex return type (priori use impl trait, then Box)
  8. Deal with return value generated by joining multiple features
  9. Compare UTXO and Balance models
  10. Realize object serialization, use the serde library
  11. Realize address generation
  12. Generate genesis block and read the data
SCRY CITY
https://preview.redd.it/rgnjtcgt6b821.png?width=1080&format=png&auto=webp&s=0112c0e7dbdff6f3fbf47ecb1f5d287e2b831881
Scheme
  1. Optimize the numerical pace of game
  2. Optimize the integrated scheme of white box
  3. Optimize the integrated numerical frame-work of white box
  4. Optimize the integrated UI process of white box
  5. Optimize product development scheme
  6. Optimize the development document list of scheme
  7. Optimize the NPC-AI behavior logic scheme
  8. Optimize the data logic flow chart
  9. Complete the city homepage scheme phase 4
  10. Complete the company homepage scheme phase 3
  11. Deduce the integrated game process
  12. Optimize the data configuration required for front and back end joint debugging
  13. Complete the art icon requirements
  14. Optimize the requirement document for talent discovery process
  15. Optimize the documents for talent storage and transaction requirements of the business.
  16. Follow up the curve drawing function of the client
  17. Follow up the retail store function of the client
  18. Optimize the map range display require-ments
  19. Optimize the requirement document for the filter function of the main interface
  20. Complete the newspaper information scheme
  21. Follow up the technology trading center program process
  22. Complete the main interface scheme
  23. Complete the offline revenue pop-up design scheme
  24. Follow up the program process of the research institute
  25. Complete the requirement document for the contract system
  26. Optimize the invention process of the research institute
  27. Follow up the company information program process
  28. Follow up the social system program process
  29. Complete the standard of city map and scene creation
  30. Optimize design system setting scheme
  31. Complete data adjustment for front and back end joint adjustment
  32. Optimize version data debugging
  33. Complete the integrated function of the trading hall and finish the flow chart
  34. Complete the modification of the construction shelf transaction process for players
  35. Optimize the advertisement space design scheme of park
  36. Complete the flow chart of new park
  37. Optimize the modified flow chart of the salary satisfaction scheme
  38. Count the function points of the next version and make deletions and adjust-ments
  39. Optimize the opening and closing process of the construction
  40. Optimize the company-talent deploy-ment scheme to make it unified with the talent exchange
  41. Optimize the research institute scheme
  42. Optimize main interface scheme design
  43. Optimize offline revenue pop-up design scheme
  44. Complete urban road resource produc-tion and data configuration
  45. Complete the data debugging for the required version
  46. Optimize the player trading scheme
  47. Complete the bubble organization of the construction land
  48. Complete the storage status classifi-cation scheme of the warehouse
  49. Complete the land and construction interface display scheme
  50. Realize the function that version timeline can be adjusted
  51. Optimize the production line adjustment process
  52. Complete the documents for the talent scheme
  53. Complete the modification of research institute scheme
  54. AI data debugging
  55. Complete talent pool data
  56. Optimize data statistics rules
  57. Complete the game guide scheme
  58. Optimize the company information scheme
  59. Optimize the main interface scheme
  60. Complete the first edition of the Spring Festival version scheme
  61. Complete the first edition of the January version scheme
  62. Optimize the trading hall process and modify the scheme
  63. Optimize the interface display scheme and bubble function
  64. Optimize the pending order operation in the building
https://preview.redd.it/dk4ypocv6b821.png?width=1080&format=png&auto=webp&s=dd63b0994ab19a79ba117d9c3dadefa035f0546d
Art
  1. Optimize the original painting feedback
  2. Optimize the basic image of Avatar
  3. Complete the original drawing of the vehicle
  4. Complete the pedestrian drawing
  5. Optimize the construction / demolition of the original painting feedback
  6. Complete friends, chat UI interface
  7. Complete the UI interface of the city information population
  8. Complete the UI slicing of the city information NPC
  9. Complete the city home page UI flow chart slicing
  10. Complete the company homepage overview UI
  11. Complete the city information NPC interface adjustment and optimization
  12. Complete the main interface of the talent center
  13. Complete the first edition of all real resources of the city
  14. Complete the basic original painting of icon body
  15. Optimized part of the missing Shader
  16. Optimize road generation standards
  17. Optimize avatar outfits
  18. Complete the talent information UI phase 1
  19. Complete land transaction and leasing UI production
  20. Optimize the research institute UI inter-face
  21. Complete the system setup UI resour-ces
  22. Optimize the UI overview of company information
  23. Complete the friend system UI slicing
  24. Complete the product icon and frame style UI optimization and addition
  25. Complete the adjustment of structure, color and keynote of real resources
  26. Construct the ambient atmosphere during the completion period (morning & day & night)
  27. Optimize the construction reflective layer (reflective materials such as windows)
  28. Optimized buildings by adding a shade for day and night alternation
  29. Complete the unified shadow direction shape
  30. Complete the construction effect in the morning, day and night ( three time periods)
  31. Complete the adjustment of structural color of the construction
  32. Optimize the shader effect of the construction
  33. Finish the black and white layer drawing of the illuminated surface of the construction
  34. Optimize the shadow shape of the construction
  35. Complete the existing product icon feedback modification
  36. Complete the drawing of the remaining commodity icons.
  37. Optimize Avatar (face / hairstyle)
  38. Complete the UI flow chart of the talent center
  39. Complete the UI production of the talent trading hall
  40. Optimize the original painting of the talent trading center
  41. Optimize the original painting of the processing factory
  42. Optimize the original painting of the raw material factory
  43. Complete all required icons for the Chinese New Year version
  44. Optimize the 3X3 original painting of the residential building
  45. Optimize the 2X2 original painting of clock tower
  46. Optimize the 3x3 original painting of office building
  47. Optimize the 3x3 original painting of supermarket
  48. Complete the UI interface of personal information (wallet)
  49. Complete the UI interface of game guidebook
  50. Completed the UI interface of operation and shutdown
  51. Complete the avatar module production method
https://preview.redd.it/mfea2hyx6b821.png?width=1080&format=png&auto=webp&s=8aa4e55fecfb0fe54f88c068dabfaba1258bb057
Client
  1. Carry out the project icon limit test
  2. Carry out the resource loading and destruction and inclusion test
  3. Complete the rpc mechanism of the controller to the model instance
  4. Split the server joint pressure
  5. Complete the table adaptive universal components
  6. Complete the interface establishment of city information
  7. Complete the function details adjustment of the raw material plant and the processing plant
  8. Complete the client UI logic and inter-face construction of retail store module
  9. Complete the UI interface of the com-pany information
  10. Complete the function of specially writing for retail store
  11. Complete the common component rewriting of the line chart
  12. Optimize the packaged exchange function
  13. Complete the homepage of the research institute and homepage and server joint
  14. Complete the structural adjustment of the research institute
  15. Complete the product interface of research institution and logic processing
  16. Complete the function of research line and invention line
  17. Complete the function of the inventive material and inventive product
  18. Optimize the interface of CreatePanel for lua universal asynchronous load resource
  19. Optimize UnitTest.Exec to satisfy the controllable requirements of the test case sequence
  20. Complete the Icon resource limit test and extend the topic for resource loading IO and memory stress testing
  21. Complete the RPC mechanism of Model and Control to achieve the effect of reflection and remotely call the corresponding Model / Ctrl method in Ctrl / Model
  22. Complete the use of RPC mechanism to rewrite the residential interface to optimize the same type of building and multi-Model mechanism at the same time
  23. Complete the fog of war
  24. Complete the fog of war scalable range and real-time refresh size to conveniently achieve the construction black screen effect when opening the UI
  25. Complete the player operation script PC / Mobile platform differentiation
  26. Complete the optional synthetic inter-face of the research institution
  27. Optimize the latest framework for residential matching
  28. Optimize the information update pro-cessing of the research invention line
  29. Optimize the modification number of employees
  30. Complete the addition and deletion function of research invention line
  31. Complete all UI logic of the research institute
  32. Complete the client UI logic of retail store module
  33. Complete the specific functions of the retail store
  34. Complete the retail store network joint debugging
  35. Complete the city information jump interface for level I and jump function
  36. Complete the city information jump interface for level II and jump function
  37. Complete the configuration table of the city information form
  38. Complete the UI logic of system sett-ings
  39. Complete the configured multi-language temporary table.
  40. Complete multi-language function localization
  41. Complete the park entry module
  42. Complete the friend system UI setup (friend management, group management, application list)
  43. Complete friend system UI resource replacement
  44. Complete the friend system server joint debugging (find, add, apply, operate, delete friends, remove blacklist shielding)
  45. Complete the Icon resource limit test
  46. Complete the refactoring resource packaging and loading process to prepare for hot fix
  47. Complete the integrated performance optimization of the client
  48. Complete the road system generation algorithm
  49. Complete the road system version 1.0 and access road resources.
  50. Complete the camera script realization (distinguish the gesture zoom/ drag/click and respond accordingly)
  51. Complete the AI of residential entrance
  52. The exchange clears all fake data
  53. Complete all logic process of the research institution for the client
  54. Complete the model code reconstruction
  55. Complete the notification server joint debugging
  56. Complete the city information configu-ration table
  57. Complete the friend interface joint debugging and fix bugs
  58. Complete the chat system UI setup
  59. Complete the chat system UI resource replacement
  60. Complete the retail store warehouse joint adjustment
  61. Complete the retail store shelf joint adjustment
  62. Complete the retail store transportation joint adjustment
  63. Complete the UI design and function process for the retail store to access park advertisement
  64. Complete the modification of the previous data store and replace Ctrl with the Modle data storage
  65. Complete the reconstruction of the technology transaction code
  66. Complete the park code reconstruction
  67. Complete camera Lua transplantation
  68. Complete the function of dragging and constructing objects
  69. Finish clicking on the building special effect lens zoom
  70. Complete the replacement of building resources 2.0
  71. Complete the architectural planning configuration table updating
  72. Complete the bubble system reserved interface function logic
  73. Complete the research server joint debugging
  74. Complete the adjustment function logic of the number of employees of the research institute.
  75. Complete other details of the research institution and bug fixes
  76. Complete the UI logic of the land transaction part
  77. Complete the model code recon-struction
  78. Optimize the login process function
  79. Complete UI logic of the talent center
  80. Complete the central warehouse selection transportation address logic
  81. Complete the scrolling logic of the main interface world chat message
  82. Complete the function of the world chat
  83. Complete the stranger information display function
  84. Complete the stranger add function
  85. Complete the stranger private chat function
  86. Complete the stranger chat function
  87. Complete the add friend function
  88. Complete the friend block function
  89. Complete the common function of multiple interface red spot notification
  90. Complete the retail store shelves and purchase goods function
  91. Complete the UI design and function of retail store access park advertising module
  92. Optimize retail store transportation system
  93. Complete the specific operation process and function of the retail store
  94. Optimize and re-adjust the production line related agreements
  95. Complete the game guide book UI logic
  96. Complete the game guide book client logic
  97. Complete the game guide book tem-porary configuration table
  98. Complete the 30-frame stress test for AOI building resource stability
https://preview.redd.it/tlinhr1y6b821.png?width=1280&format=png&auto=webp&s=501ad2e40c9ef3d5951c261f46f19fdd53017b71
Server
  1. Optimize the technology center server joint debugging
  2. Complete AI function phase 3
  3. Conduct research institute server joint debugging
  4. Complete AI functions and associated building functions
  5. Complete the statistical server frame-work
  6. Complete the social friend system server development (add, delete, status update)
  7. Complete the blacklist function of server development
  8. Complete the offline friend adding function development
  9. Complete the visual log function of AI
  10. Complete the construction of front and back end of the HTTP server
  11. Complete the function to fix bug
  12. Follow up the server-side mailbox system code writing and improvement
  13. Complete the mail system function of the client joint adjustment
  14. Complete the related function of the friend chat server
  15. Complete the related function of the stranger chat server
  16. Complete the related function of the world channel chat server
  17. Complete the related function of friends and strangers offline message server
  18. Complete the land auction change coding (rental time and purchase price display, etc.)
  19. Complete the bug fix of the AI, shelf, city urban area calculation and other functions
  20. Complete AI-log adjustment
  21. Complete all basic social function joint debugging
  22. Optimize the blacklist limit function
Operation & marketing
  1. Scry.Info participates in the Microsoft Accelerator Alumni Return Day event
  2. Scry.Info builds overseas communities
submitted by StephenCuuuurry to SCRYDDD [link] [comments]

New to Mining: Crashing afrer running Claymore's Dual Ethereum, Phoenix 3.0 & Genoiil

As title states, I'm experiencing crashes shortly after running the mining exe. on the latest versions of these miners. Ironically enough Finminer works just fine for me, but it isn't highly recommended here so I really want to get these 3 working specifically Claymore. Here is a copy of the log for claymore .........
08:42:19:620 3dd8 Check and remove old log files... 08:42:19:621 3dd8 args: eth-us-east1.nanopool.org:8888 -ewal 0x6216049f1eD2b73ae1df2D07e5003856AA61d9F6/Sudestbrew/[email protected] -mode 1 08:42:19:622 3dd8 08:42:19:622 3dd8 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 08:42:19:622 3dd8 º Claymore's Dual GPU Miner - v11.9 º 08:42:19:623 3dd8 º ETH + DCSIA/LBC/PASC/BLAKE2S/KECCAK º 08:42:19:623 3dd8 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 08:42:19:624 3dd8 08:42:19:624 3dd8 b597 08:42:19:828 3dd8 ETH: 6 pools are specified 08:42:19:834 3dd8 Main Ethereum pool is eth-us-west1.nanopool.org:9999 08:42:19:863 3dd8 OpenCL platform: NVIDIA CUDA 08:42:19:864 3dd8 AMD OpenCL platform not found 08:42:19:967 3dd8 CUDA initializing...
08:42:19:973 3dd8 NVIDIA Cards available: 1 08:42:19:974 3dd8 CUDA Driver Version/Runtime Version: 9.2/7.5 08:42:19:977 3dd8 GPU #0: GeForce GTX 1080, 8192 MB available, 20 compute units, capability: 6.1 (pci bus 1:0:0) 08:42:19:977 3dd8 Total cards: 1 08:42:23:983 3dd8 You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.
08:42:24:987 3dd8 NVML version: 9.398.36 08:42:24:996 3dd8 NVML: cannot get fan speed, error 3 08:42:25:457 3dd8 SSL: Imported 52 certificates from local storage 08:42:25:469 744 ETH: Stratum - connecting to 'eth-us-west1.nanopool.org' <45.76.65.223> port 9999 (unsecure) 08:42:25:561 3dd8 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
08:42:25:562 3dd8 ETH: eth-proxy stratum mode 08:42:25:563 3dd8 Watchdog enabled 08:42:25:564 3dd8 Remote management (READ-ONLY MODE) is enabled on port 3333 08:42:25:565 3dd8
08:42:25:590 744 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x6216049f1ed2b73ae1df2d07e5003856aa61d9f6.x6/[email protected]", "x"], "id": 2, "method": "eth_submitLogin"}
08:42:25:591 744 ETH: Stratum - Connected (eth-us-west1.nanopool.org:9999) (unsecure) 08:42:25:837 67c NVML: cannot get fan speed, error 3 08:42:25:992 744 buf: {"jsonrpc":"2.0","id":2,"result":true} {"jsonrpc":"2.0","id":0,"result":["0x7b91118cb58da9cc3cfe7e92fea5b5e93929f21e50d969544a8b34b7db19c59d","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:25:995 744 ETH: Authorized 08:42:25:996 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:42:25:996 744 remove first packet 243 08:42:26:013 44b8 Setting DAG epoch #202... 08:42:26:256 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x7b91118cb58da9cc3cfe7e92fea5b5e93929f21e50d969544a8b34b7db19c59d","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:27:741 44b8 Setting DAG epoch #202 for GPU0 08:42:27:744 44b8 Create GPU buffer for GPU0 08:42:28:841 67c NVML: cannot get fan speed, error 3 08:42:31:845 67c NVML: cannot get fan speed, error 3 08:42:34:849 67c NVML: cannot get fan speed, error 3 08:42:36:005 744 ETH: checking pool connection... 08:42:36:010 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:42:36:287 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x7b91118cb58da9cc3cfe7e92fea5b5e93929f21e50d969544a8b34b7db19c59d","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:37:852 67c NVML: cannot get fan speed, error 3 08:42:38:321 44b8 GPU0 DAG creation time - 10482 ms 08:42:38:327 44b8 Setting DAG epoch #202 for GPU0 done 08:42:39:271 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x1fb26cbd23507a578e306841ed0538bfa0b1cb88448140c0f32aae7673f3ff3c","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:39:274 744 ETH: 08/01/18-08:42:39 - New job from eth-us-west1.nanopool.org:9999 08:42:39:275 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:42:39:275 744 ETH - Total Speed: 20.812 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 08:42:39:276 744 ETH: GPU0 20.812 Mh/s 08:42:40:857 67c NVML: cannot get fan speed, error 3 08:42:43:861 67c NVML: cannot get fan speed, error 3 08:42:44:622 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x3120548c380d7bb4071a142b88aebdbd25371f8ed4e9203df361fa656ae5ff81","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:44:622 744 ETH: 08/01/18-08:42:44 - New job from eth-us-west1.nanopool.org:9999 08:42:44:622 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:42:44:623 744 ETH - Total Speed: 20.865 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 08:42:44:624 744 ETH: GPU0 20.865 Mh/s 08:42:46:006 744 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x13dbe77", "0x000000000000000000000000000000000000000000000000000000001aaa687c"]}
08:42:46:021 744 ETH: checking pool connection... 08:42:46:021 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:42:46:370 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x3120548c380d7bb4071a142b88aebdbd25371f8ed4e9203df361fa656ae5ff81","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:46:866 67c NVML: cannot get fan speed, error 3 08:42:47:035 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x895e6ff75b81f4aa9956f8d2b505bd6d4b71e637ef5c9e419eb2363902733e7e","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:47:038 744 ETH: 08/01/18-08:42:47 - New job from eth-us-west1.nanopool.org:9999 08:42:47:039 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:42:47:039 744 ETH - Total Speed: 20.827 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 08:42:47:040 744 ETH: GPU0 20.827 Mh/s 08:42:49:870 67c NVML: cannot get fan speed, error 3 08:42:49:873 67c NVML: cannot get fan speed, error 3 08:42:49:874 67c GPU0 t=63C fan=0% 08:42:49:996 2590 em hbt: 0, fm hbt: 94, 08:42:49:999 2590 watchdog - thread 0 (gpu0), hb time 188 08:42:49:999 2590 watchdog - thread 1 (gpu0), hb time 438 08:42:51:638 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x3e62d60b58c711a1a853b7eb3ec9fa12217aa238c8955738aa207d5a7c6b9953","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:51:641 744 ETH: 08/01/18-08:42:51 - New job from eth-us-west1.nanopool.org:9999 08:42:51:644 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:42:51:645 744 ETH - Total Speed: 20.867 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 08:42:51:646 744 ETH: GPU0 20.867 Mh/s 08:42:52:876 67c NVML: cannot get fan speed, error 3 08:42:55:882 67c NVML: cannot get fan speed, error 3 08:42:56:036 744 ETH: checking pool connection... 08:42:56:039 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:42:56:284 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x3e62d60b58c711a1a853b7eb3ec9fa12217aa238c8955738aa207d5a7c6b9953","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:42:58:886 67c NVML: cannot get fan speed, error 3 08:43:01:890 67c NVML: cannot get fan speed, error 3 08:43:04:894 67c NVML: cannot get fan speed, error 3 08:43:06:021 744 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x13e1f81", "0x000000000000000000000000000000000000000000000000000000001aaa687c"]}
08:43:06:053 744 ETH: checking pool connection... 08:43:06:056 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:43:06:405 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x3e62d60b58c711a1a853b7eb3ec9fa12217aa238c8955738aa207d5a7c6b9953","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:07:898 67c NVML: cannot get fan speed, error 3 08:43:10:902 67c NVML: cannot get fan speed, error 3 08:43:12:308 744 buf: {"jsonrpc":"2.0","id":0,"result":["0xbd07a0072edb08a99823396baf1c959e90e9ce84ead3b603c9c3d2ab13435b06","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:12:311 744 ETH: 08/01/18-08:43:12 - New job from eth-us-west1.nanopool.org:9999 08:43:12:314 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:43:12:315 744 ETH - Total Speed: 20.621 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 08:43:12:316 744 ETH: GPU0 20.621 Mh/s 08:43:13:906 67c NVML: cannot get fan speed, error 3 08:43:16:067 744 ETH: checking pool connection... 08:43:16:070 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:43:16:341 744 buf: {"jsonrpc":"2.0","id":0,"result":["0xbd07a0072edb08a99823396baf1c959e90e9ce84ead3b603c9c3d2ab13435b06","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:16:910 67c NVML: cannot get fan speed, error 3 08:43:19:914 67c NVML: cannot get fan speed, error 3 08:43:19:917 67c NVML: cannot get fan speed, error 3 08:43:19:918 67c GPU0 t=66C fan=0% 08:43:20:162 2590 em hbt: 16, fm hbt: 110, 08:43:20:165 2590 watchdog - thread 0 (gpu0), hb time 47 08:43:20:168 2590 watchdog - thread 1 (gpu0), hb time 297 08:43:22:920 67c NVML: cannot get fan speed, error 3 08:43:25:926 67c NVML: cannot get fan speed, error 3 08:43:26:036 744 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x139f68e", "0x000000000000000000000000000000000000000000000000000000001aaa687c"]}
08:43:26:084 744 ETH: checking pool connection... 08:43:26:084 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:43:26:417 744 buf: {"jsonrpc":"2.0","id":0,"result":["0xbd07a0072edb08a99823396baf1c959e90e9ce84ead3b603c9c3d2ab13435b06","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:28:930 67c NVML: cannot get fan speed, error 3 08:43:31:934 67c NVML: cannot get fan speed, error 3 08:43:34:939 67c NVML: cannot get fan speed, error 3 08:43:36:099 744 ETH: checking pool connection... 08:43:36:100 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:43:36:367 744 buf: {"jsonrpc":"2.0","id":0,"result":["0xbd07a0072edb08a99823396baf1c959e90e9ce84ead3b603c9c3d2ab13435b06","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:37:940 67c NVML: cannot get fan speed, error 3 08:43:40:943 67c NVML: cannot get fan speed, error 3 08:43:43:949 67c NVML: cannot get fan speed, error 3 08:43:46:053 744 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x13ed63d", "0x000000000000000000000000000000000000000000000000000000001aaa687c"]}
08:43:46:115 744 ETH: checking pool connection... 08:43:46:116 744 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
08:43:46:445 744 buf: {"jsonrpc":"2.0","id":0,"result":["0xbd07a0072edb08a99823396baf1c959e90e9ce84ead3b603c9c3d2ab13435b06","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:46:953 67c NVML: cannot get fan speed, error 3 08:43:48:917 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x4c36d871f9e3387b9d3c8eb5ed46c0bffcac03f8056623f6b004a774e45612ed","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:48:920 744 ETH: 08/01/18-08:43:48 - New job from eth-us-west1.nanopool.org:9999 08:43:48:921 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:43:48:921 744 ETH - Total Speed: 20.876 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:01 08:43:48:922 744 ETH: GPU0 20.876 Mh/s 08:43:49:958 67c NVML: cannot get fan speed, error 3 08:43:49:961 67c NVML: cannot get fan speed, error 3 08:43:49:962 67c GPU0 t=69C fan=0% 08:43:50:337 2590 em hbt: 0, fm hbt: 0, 08:43:50:340 2590 watchdog - thread 0 (gpu0), hb time 141 08:43:50:340 2590 watchdog - thread 1 (gpu0), hb time 407 08:43:52:963 67c NVML: cannot get fan speed, error 3 08:43:53:674 744 buf: {"jsonrpc":"2.0","id":0,"result":["0x577dcf5472c52bd8dfbb9cd1f429ed558629d8b4659d09284b6c361c670577e9","0xf79b52b49b7c6f27ac46f1dae8ec9ba109677010a0b9b7afda231cee90bc1ea9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
08:43:53:676 744 ETH: 08/01/18-08:43:53 - New job from eth-us-west1.nanopool.org:9999 08:43:53:677 744 target: 0x000000006df37f67 (diff: 10000MH), epoch 202(2.58GB) 08:43:53:678 744 ETH - Total Speed: 20.817 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:01 08:43:53:679 744 ETH: GPU0 20.817 Mh/s
I will post my batch file info in reply.
Thanks guys.
submitted by Sudestbrewer to EtherMining [link] [comments]

Socket was closed remotely (by pool) ETH: Connection lost, retry in 20 sec...

Windows 10 8GB ram (6) GTX1070s running claymore miner 10.2
setx GPU_FORCE_64BIT_PTR 0 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100 
EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal myetheraddresshere.minernamehere/[email protected] -epsw x -mode 1 -ftime 10
Everything worked fine for months and then I started getting the "socket was closed remotely" message 3 days ago. I checked the log and see the following errors
10:24:30:988 14c0 Check and remove old log files... 10:24:30:995 14c0 args: -epool eth-eu1.nanopool.org:9999 -ewal 0xD583ef08d5df431Fe2CCF69B3Aa52dbD5b8A4b85.lrminer154/[email protected] -epsw x -mode 1 -ftime 10 10:24:30:998 14c0 10:24:31:001 14c0 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 10:24:31:003 14c0 º Claymore's Dual ETH + DCSC/LBC/PASC GPU Miner v10.2 º 10:24:31:006 14c0 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 10:24:31:009 14c0 10:24:31:212 14c0 ETH: 3 pools are specified 10:24:31:222 14c0 Main Ethereum pool is eth-eu1.nanopool.org:9999 10:24:31:475 14c0 OpenCL platform: Intel(R) OpenCL 10:24:31:478 14c0 OpenCL platform: NVIDIA CUDA 10:24:31:480 14c0 AMD OpenCL platform not found 10:24:31:861 14c0 CUDA initializing... 10:24:31:863 14c0 NVIDIA Cards available: 6 10:24:31:866 14c0 CUDA Driver Version/Runtime Version: 9.1/8.0 10:24:31:952 14c0 GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 10:24:31:959 14c0 GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 10:24:31:966 14c0 GPU #2: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 10:24:31:973 14c0 GPU #3: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 10:24:31:980 14c0 GPU #4: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 10:24:31:988 14c0 GPU #5: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1 10:24:31:991 14c0 Total cards: 6 10:24:36:001 14c0 No AMD cards in the list, ADL library will not be used. 10:24:36:011 14c0 NVML version: 9.388.31 10:24:36:704 2e4 ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <213.32.29.168> port 9999 10:24:36:799 14c0 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1) 10:24:36:811 14c0 ETH: eth-proxy stratum mode 10:24:36:818 14c0 Watchdog enabled 10:24:36:821 14c0 Remote management (READ-ONLY MODE) is enabled on port 3333 10:24:36:824 14c0 10:24:36:824 2e4 send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xD583ef08d5df431Fe2CCF69B3Aa52dbD5b8A4b85.lrminer154/[email protected]", "x"], "id": 2, "method": "eth_submitLogin"} 10:24:36:829 2e4 ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) 10:24:36:964 2e4 got 282 bytes 10:24:36:975 2e4 buf: {"jsonrpc":"2.0","id":2,"result":true} {"jsonrpc":"2.0","id":0,"result": 
["0x0dd5460f21bce408bf2d326e9086a9484be90f614b8cc75fe0b9db2be6489fd6","0x1e9891b51a83da3e735c71999400fc8927e8614e86fc37e618d3781578d5c939","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
10:24:36:985 2e4 parse packet: 38 10:24:36:991 2e4 ETH: Authorized 10:24:36:996 2e4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"} 10:24:37:000 2e4 remove first packet 243 10:24:37:004 2e4 new buf size: 243 10:24:37:008 2e4 parse packet: 242 10:24:37:011 2e4 ETH: job changed 10:24:37:014 2e4 new buf size: 0 10:24:37:109 18e0 Setting DAG epoch #155... 10:24:37:129 2e4 got 243 bytes 10:24:37:131 2e4 buf: {"jsonrpc":"2.0","id":0,"result": ["0x0dd5460f21bce408bf2d326e9086a9484be90f614b8cc75fe0b9db2be6489fd6","0x1e9891b51a83da3e735c71999400fc8927e8614e86fc37e618d3781578d5c939","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]} 10:24:37:134 2e4 parse packet: 242 10:24:37:136 2e4 ETH: job is the same 10:24:37:139 2e4 new buf size: 0 10:24:38:654 15b4 Setting DAG epoch #155 for GPU5 10:24:38:653 18e0 Setting DAG epoch #155 for GPU0 10:24:38:654 191c Setting DAG epoch #155 for GPU1 10:24:38:654 189c Setting DAG epoch #155 for GPU3 10:24:38:657 668 Setting DAG epoch #155 for GPU4 10:24:38:665 1010 Setting DAG epoch #155 for GPU2 10:24:38:672 15b4 Create GPU buffer for GPU5 10:24:38:668 18e0 Create GPU buffer for GPU0 10:24:38:669 668 Create GPU buffer for GPU4 10:24:38:681 1010 Create GPU buffer for GPU2 10:24:38:677 191c Create GPU buffer for GPU1 10:24:38:666 189c Create GPU buffer for GPU3 10:24:43:126 2e4 got 243 bytes 10:24:43:132 2e4 buf: {"jsonrpc":"2.0","id":0,"result":["0x8f68ba58d8f6d17f5ab125baa124dfe533e3637200d2d6981a32490ae5f2df6f","0x1e9891b51a83da3e735c71999400fc8927e8614e86fc37e618d3781578d5c939","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]} 10:24:43:138 2e4 parse packet: 242 10:24:43:141 2e4 ETH: job changed 10:24:43:144 2e4 new buf size: 0 10:24:43:147 2e4 ETH: 12/04/17-10:24:43 - New job from eth-eu1.nanopool.org:9999 10:24:43:149 2e4 target: 0x00000000dbe6fece (diff: 5000MH), epoch 155(2.21GB) 10:24:43:152 2e4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 10:24:43:155 2e4 ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s 10:24:45:091 15b4 GPU5 DAG creation time - 6245 ms 10:24:45:096 15b4 Setting DAG epoch #155 for GPU5 done 10:24:45:096 18e0 GPU0 DAG creation time - 6243 ms 10:24:45:102 18e0 Setting DAG epoch #155 for GPU0 done 10:24:45:121 668 GPU4 DAG creation time - 6268 ms 10:24:45:124 668 Setting DAG epoch #155 for GPU4 done 10:24:45:128 191c GPU1 DAG creation time - 6271 ms 10:24:45:131 191c Setting DAG epoch #155 for GPU1 done 10:24:45:154 189c GPU3 DAG creation time - 6290 ms 10:24:45:157 189c Setting DAG epoch #155 for GPU3 done 10:24:45:165 1010 GPU2 DAG creation time - 6308 ms 10:24:45:169 1010 Setting DAG epoch #155 for GPU2 done 10:24:47:031 2e4 ETH: checking pool connection... 10:24:47:037 2e4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"} 10:24:55:528 189c ETH: put share nonce bcf3e2e00989e590 10:24:55:536 189c ETH round found 1 shares 10:24:55:539 2e4 ETH: 12/04/17-10:24:55 - SHARE FOUND - (GPU 3) 10:24:55:542 2e4 send: {"id":13,"method":"eth_submitWork","params":["0xbcf3e2e00989e590","0x8f68ba58d8f6d17f5ab125baa124dfe533e3637200d2d6981a32490ae5f2df6f","0x2b2083086fa9217385f3da888d21cef4443e12e5bf4209615d42208c2fef2190"]} 10:24:57:032 2e4 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xb3d6690", "0x00000000000000000000000000000000000000000000000000000000fad81c3d"]} 10:24:57:046 2e4 ETH: checking pool connection... 10:24:57:050 2e4 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"} 10:24:58:992 1010 ETH: put share nonce beadcf200cb8ec2e 10:24:58:995 1010 ETH round found 1 shares 10:24:58:997 2e4 ETH: 12/04/17-10:24:58 - SHARE FOUND - (GPU 2) 10:24:59:001 2e4 send: {"id":12,"method":"eth_submitWork","params":["0xbeadcf200cb8ec2e","0x8f68ba58d8f6d17f5ab125baa124dfe533e3637200d2d6981a32490ae5f2df6f","0xc3f217b7eb7831e6534469db15c6114c4321e9035c47ab43d7d5d430a5c3631f"]} 10:25:01:261 14d8 GPU0 t=42C fan=27%, GPU1 t=43C fan=27%, GPU2 t=42C fan=27%, GPU3 t=39C fan=27%, GPU4 t=40C fan=27%, GPU5 t=45C fan=28% 10:25:01:307 1328 em hbt: 0, fm hbt: 16, 10:25:01:320 1328 watchdog - thread 0 (gpu0), hb time 62 10:25:01:327 1328 watchdog - thread 1 (gpu0), hb time 187 10:25:01:330 1328 watchdog - thread 2 (gpu1), hb time 188 10:25:01:333 1328 watchdog - thread 3 (gpu1), hb time 63 10:25:01:335 1328 watchdog - thread 4 (gpu2), hb time 219 10:25:01:338 1328 watchdog - thread 5 (gpu2), hb time 94 10:25:01:341 1328 watchdog - thread 6 (gpu3), hb time 47 10:25:01:343 1328 watchdog - thread 7 (gpu3), hb time 172 10:25:01:346 1328 watchdog - thread 8 (gpu4), hb time 204 10:25:01:349 1328 watchdog - thread 9 (gpu4), hb time 79 10:25:01:351 1328 watchdog - thread 10 (gpu5), hb time 219 10:25:01:354 1328 watchdog - thread 11 (gpu5), hb time 94 10:25:04:980 668 ETH: put share nonce 50b09f9012679889 10:25:04:983 668 ETH round found 1 shares 10:25:04:985 2e4 ETH: 12/04/17-10:25:04 - SHARE FOUND - (GPU 4) 10:25:04:988 2e4 send: {"id":14,"method":"eth_submitWork","params":["0x50b09f9012679889","0x8f68ba58d8f6d17f5ab125baa124dfe533e3637200d2d6981a32490ae5f2df6f","0xfeeb1300c8bc6294c2ee7169cae91644b169f212bdb798980c05dc08b9e3e8be"]} 10:25:06:255 2e4 Socket was closed remotely (by pool) 10:25:06:264 2e4 ETH: Connection lost, retry in 20 sec... 
submitted by 844bankbtc to EtherMining [link] [comments]

Android browser for Ethereum, a possible approach.

This is a (proof of concept) android ethereum/web3 browser, like Parity/mist but for android, it's attached to a JSONRPC node from Infura.
This is the GitHub Repo, feel free to take a look, judge the approach.
This is the pre-alpha android app (3mb).
Although it does give up the independence of running your own node, this approach was chosen for its relative small size and easy on the data approach.
If you're a developer:
submitted by chimpAssist to ethereum [link] [comments]

Is there a Golang Ethereum JSON client package?

Is there a Golang Ethereum JSON client package? submitted by ThePiachu to ethereum [link] [comments]

Why does this jsonrpc call get stuck?

I have go-ethereum running as a daemon and synced, but can't get a new address with curl, this is what I'm using in the command line:
curl --data-binary '{"jsonrpc":"2.0", "id":1, "method": "personal_newAccount", "params":["pass"] }' -H 'accept: application/json;' -H 'content-type: application/json;' http://localhost:8545 
After I run the command the terminal get's stuck and I have to press CTRL-C to get to the command prompt again.
submitted by rraallvv to ethereum [link] [comments]

My GPU crashes as soon as I start mining on nanopool and other pools.

As stated in the title, my GPU crashes whenever I start mining. Since I'm new to mining, I dont know if there is something obviously wrong. This ist the Logfile:
22:11:35:331 1854 args: -epool eth-eu1.nanopool.org:9999 -ewal wallet.Arthumail -epsw x -mode 1 -ftime 10 22:11:35:465 1854 22:11:35:466 1854 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 22:11:35:466 1854 º Claymore's Dual ETH + DCSC/LBC/PASC GPU Miner v10.0 º 22:11:35:466 1854 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 22:11:35:466 1854 22:11:35:667 1854 ETH: 5 pools are specified 22:11:35:667 1854 Main Ethereum pool is eth-eu1.nanopool.org:9999 22:11:35:704 1854 OpenCL platform: NVIDIA CUDA 22:11:35:705 1854 AMD OpenCL platform not found 22:11:35:868 1854 CUDA initializing...
22:11:35:868 1854 NVIDIA Cards available: 1 22:11:35:868 1854 CUDA Driver Version/Runtime Version: 9.1/8.0 22:11:35:869 1854 GPU #0: GeForce GTX 980 Ti, 6144 MB available, 22 compute units, capability: 5.2
22:11:35:869 1854 Total cards: 1 22:11:39:870 1854 No AMD cards in the list, ADL library will not be used. 22:11:39:872 1854 NVML version: 9.388.43 22:11:39:924 6c8 ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <207.154.213.72> port 9999 22:11:39:953 6c8 send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["wallet.Arthumail", "x"], "id": 2, "method": "eth_submitLogin"}
22:11:39:953 6c8 ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) 22:11:39:984 6c8 got 282 bytes 22:11:39:984 6c8 buf: {"jsonrpc":"2.0","id":2,"result":true} {"jsonrpc":"2.0","id":0,"result":["0x34f807c46a67f5236765f051648c9bdadde11135b1991beef2a686fba4f12d57","0x7b1e42ac7d205c8da33a3dea0e5fd6aa0261c13f0a8e451454721085d1323eec","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
22:11:39:984 6c8 parse packet: 38 22:11:39:985 6c8 ETH: Authorized 22:11:39:985 6c8 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
22:11:39:985 6c8 remove first packet 243 22:11:39:985 6c8 new buf size: 243 22:11:39:985 6c8 parse packet: 242 22:11:39:985 6c8 ETH: job changed 22:11:39:985 6c8 new buf size: 0 22:11:40:008 6c8 got 243 bytes 22:11:40:008 6c8 buf: {"jsonrpc":"2.0","id":0,"result":["0x34f807c46a67f5236765f051648c9bdadde11135b1991beef2a686fba4f12d57","0x7b1e42ac7d205c8da33a3dea0e5fd6aa0261c13f0a8e451454721085d1323eec","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
22:11:40:008 6c8 parse packet: 242 22:11:40:009 6c8 ETH: job is the same 22:11:40:009 6c8 new buf size: 0 22:11:40:018 1854 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
22:11:40:018 1854 ETH: eth-proxy stratum mode 22:11:40:018 1854 Watchdog enabled 22:11:40:018 1854 Remote management (READ-ONLY MODE) is enabled on port 3333 22:11:40:018 1854
22:11:40:020 462c Setting DAG epoch #156... 22:11:41:493 462c Setting DAG epoch #156 for GPU0 22:11:41:494 462c Create GPU buffer for GPU0 22:11:47:089 462c GPU0 DAG creation time - 5403 ms 22:11:47:089 462c Setting DAG epoch #156 for GPU0 done 22:11:49:994 6c8 ETH: checking pool connection... 22:11:49:994 6c8 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
22:11:50:022 6c8 got 243 bytes 22:11:50:022 6c8 buf: {"jsonrpc":"2.0","id":0,"result":["0x34f807c46a67f5236765f051648c9bdadde11135b1991beef2a686fba4f12d57","0x7b1e42ac7d205c8da33a3dea0e5fd6aa0261c13f0a8e451454721085d1323eec","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
22:11:50:022 6c8 parse packet: 242 22:11:50:022 6c8 ETH: job is the same 22:11:50:022 6c8 new buf size: 0 22:11:56:783 1f3c NVML: cannot get current temperature, error 999 (an internal driver error occurred) 22:11:56:783 1f3c NVML: cannot get fan speed, error 999 (an internal driver error occurred) 22:11:56:882 33d8 GPU 0, GpuMiner cu_k1 failed 30, unknown error 22:11:56:885 33d8 GPU 0, GpuMiner kx failed 1 22:11:56:885 33d8 Set global fail flag, failed GPU0 22:11:56:885 33d8 GPU 0 failed 22:11:56:885 462c GPU 0, GpuMiner cu_k1 failed 30, unknown error 22:11:56:886 462c GPU 0, GpuMiner kx failed 1 22:11:56:886 462c Set global fail flag, failed GPU0 22:11:56:886 462c GPU 0 failed 22:11:59:846 1f3c NVML: cannot get current temperature, error 999 (an internal driver error occurred) 22:11:59:846 1f3c NVML: cannot get fan speed, error 999 (an internal driver error occurred) 22:11:59:993 6c8 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x0000000000000000000000000000000000000000000000000000000074495aa4"]}
22:12:00:009 6c8 ETH: checking pool connection... 22:12:00:009 6c8 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
22:12:00:075 6c8 got 243 bytes 22:12:00:075 6c8 buf: {"jsonrpc":"2.0","id":0,"result":["0x34f807c46a67f5236765f051648c9bdadde11135b1991beef2a686fba4f12d57","0x7b1e42ac7d205c8da33a3dea0e5fd6aa0261c13f0a8e451454721085d1323eec","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
22:12:00:075 6c8 parse packet: 242 22:12:00:075 6c8 ETH: job is the same 22:12:00:075 6c8 new buf size: 0 22:12:02:799 6c8 got 243 bytes 22:12:02:799 6c8 buf: {"jsonrpc":"2.0","id":0,"result":["0xcb0aa53d560675cf25aeaa368d62dcf425e3c041ddfe3d14242493cc09ae40bd","0x7b1e42ac7d205c8da33a3dea0e5fd6aa0261c13f0a8e451454721085d1323eec","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
22:12:02:799 6c8 parse packet: 242 22:12:02:799 6c8 ETH: job changed 22:12:02:799 6c8 new buf size: 0 22:12:08:402 1f3c NVML: cannot get current temperature, error 999 (an internal driver error occurred) 22:12:08:402 6c8 ETH: 12/07/17-22:12:02 - New job from eth-eu1.nanopool.org:9999 22:12:08:403 1f3c NVML: cannot get fan speed, error 999 (an internal driver error occurred) 22:12:08:403 6c8 target: 0x00000000dbe6fece (diff: 5000MH), epoch 156(2.22GB) 22:12:08:403 6c8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 22:12:08:403 6c8 ETH: GPU0 0.000 Mh/s 22:12:08:630 32bc Quit... 22:12:08:684 32bc NVML: cannot get current temperature, error 999 (an internal driver error occurred) 22:12:08:684 32bc NVML: cannot get fan speed, error 999 (an internal driver error occurred)*
And my batch looks like this:
EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal walet.Arthumail -epsw x -mode 1 -ftime 10
I'm using a 980ti and a 6700k. The GPU crashes too if I mine on other pools. The wallet and mail are just placeholders. There is my real wallet and mail written in the batch file. Thanks for helping in advance.
submitted by Arthur199 to EtherMining [link] [comments]

How is the Ethershift works platform.

How is the Ethershift works platform.
To exchange tokens, users send value to a special address (which indicates the type of token they would like to receive back) and the exchanged value will be sent back to them at the address they sent the original tokens from. This user experience is implemented by fulfilling the exchange using hot wallets, and then later mirroring the trade (at a hopefully equivalent rate) on an exchange, and periodically re-balancing the exchange/hot wallets. Ethershift takes a cut of profit (half of it in the form of the input token, half of it in the form of the output token) to account for the risk of the exchange rate changing. Third-parties are able to integrate Ethershift into their own systems and receive a 50% cut of the profit via the Ethershift API. The back-end service is an application written in Node JS, running on Amazon EC2. To access the Ethereum network, a full node is installed on the server, and the back-end service communicates with it through its JSONRPC API. The service uses an SQL database to keep track of profits. https://ethershift.co/

https://preview.redd.it/go8sqww2y2321.jpg?width=1080&format=pjpg&auto=webp&s=52d1606d26678ed99c6ebab6d71f8ffbf61c051c
submitted by venbusiness to Crypto_ico [link] [comments]

enAPI: nodeJS json-rpc 2.0 API and tools 03. Web3.js Tutorial - Attach a GUI to your Ethereum Smart ... Bitcoin JSON-RPC Tutorial 6 - JSON Parameters and Errors Deploy A Smart Contract With Web3 (1.0)  Ep 3 Bitcoin JSON-RPC Tutorial 7 - Wallet Notify

DEPRECATED! Java implementation of the Ethereum yellowpaper. For JSON-RPC and other client features check Ethereum Harmony - Ethereum-eternity/ethereumj Ethereum JSON-RPC APIs use a name-space system. RPC methods are grouped into several categories depending on their purpose. All method names are composed of the namespace, an underscore, and the actual method name within the namespace. For example, the eth_call method resides in the eth namespace. Access to RPC methods can be enabled on a per ... ¶ JSON RPC API. JSON is a lightweight data-interchange format. It can represent numbers, strings, ordered sequences of values, and collections of name/value pairs. JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol. Primarily this specification defines several data structures and the rules around their processing. 外部からGethにアクセスするために必要なJSON RPCについて書いていきます。 Category About Ethereum(Geth)でJSON RPCを使って外部からアクセスする Geth. 公開: 2018-01-28. 更新: 2020-04-29. こんにちは、いつもお読みいただきありがとうございます。 ... The JSON-RPC format expects eth_call to have a specific data field format that requires normalizing the contract function balanceOf to a short Function Selector. To do this, we take out the names and the type of inputs it takes, and take that as a string. We then run it through Ethereum’s sha3 keccak hash:

[index] [4343] [3503] [6243] [2130] [6321] [6829] [600] [2764] [1086] [1585]

enAPI: nodeJS json-rpc 2.0 API and tools

Ethereum é uma tecnologia relativamente nova que está abalando o ecossistema das criptomoedas. Diferente do Bitcoin, ela é concebida para ser uma plataforma ... Free Course Page (In development): https://goo.gl/EiKpPP Written tutorial of this video: https://goo.gl/RdXuz9 https://coursetro.com This video is the 3rd le... Today we are going to deploy an Ethereum smart contract to a local testnet: - Using web3 for the JSON RPC client - Using Ethereumjs-testrpc for the Ethereum client - Using an interactive nodejs ... Bitcoin JSON-RPC tutorial. How to set up and use bitcoind wallet notify feature. ... Ethereum 2.0 News, ETH Price Prediction & ETH Airdrop with Vitalik Buterin Ethereum Foundation 이더 리움 ... enAPI: nodeJS json-rpc 2.0 API and tools to easily spin up ethereum based blockchain nodes and build dapps. Below are all the links mentioned in the video and extra resources GitHub https://github ...

http://binary-option-trade-arab.farmporn.eu