Consistently getting the "Problem communicating with

complete newbie: "Problems communicating with bitcoin RPC 0 2" ?

i saw somewhere that the bitcoin client needs to download all blocks before i can start mining.. is this possibly the reason i'm getting this error right now, while the client is still retrieving blocks?
i can't seem to find a definitive answer anywhere else.
submitted by alefnull to mtred [link] [comments]

Is MtRed Down?

I am current getting a "Problems communicating with bitcoin RPC 2 2, 1 2, 0 2
submitted by laweinhander to mtred [link] [comments]

First time trying mtred, and I get this..

2011-06-23 16:15:36: Listener for "Default": 23/06/2011 16:15:36, Problems communicating with bitcoin RPC
Any ideas on how to fix it so I can mine with redditors? (using GUIminer for this)
submitted by hyperhopper to mtred [link] [comments]

I cannot get connected to MtRed. Any ideas?

8337 is forwarded. Using "http://MtRed.com" as host. Even have my PC in the DMZ but cannot get rid of the "Problems communicating with bitcoin RPC" error.
submitted by ZachSka87 to Bitcoin [link] [comments]

"Problems communicating with Bitcoin RPC" even while mining?

I can't figure out what is going on. I am mining, and submitting shares, but even though I have the same hash rate, I'm submitting shares at a much slower rate than on other pools. I'd prefer to use MTRed, but unless I can get this solved I'm not sure I will.
So I was watching the miner, and where it shows a live stat of my hash count it will sometimes flash the text "Problems communicating with bitcoin RPC" and then continue mining. Everything I find on that error seems to be about not being able to connect at all, but I can connect and mine, just not as efficiently as I should be able to.
Here is the command I'm running (Win 7):
poclbm.exe --platform 1 -d 1 -v -w 128 -f 60 -a 15 --user=username --pass=pass -o mtred.com -p 8337 
I also tried this, which gives me a higher hashrate so I'd like to figure out why so I can keep mining at that rate, but frequent "long polls" and still gives the RPC error:
poclbm.exe --platform 1 -d 1 --user=username --pass=pass -o mtred.com -p 8337
Any help is greatly appreciated!
EDIT: It sounds like it is a known issue. Any ideas on the long polling? Is that even a problem?
submitted by ferrarisnowday to mtred [link] [comments]

Help with getting GUIMiner working on MtRed

Simple question. I use GUIMiner with slush's pool, with my extra flags set to "-s0.006" which is used to adjust how often the video card sleeps to keep it cool.
I've created my account and a worker on Mtred. I created a new OpenCL miner, chose "Other" as the server and put in mtred.com as the host. I put in my Username as "name.workername" and password is the worker password. When I start mining it says "Problems communicating with bitcoin RPC".
Can someone tell where I'm falling short? I'm sure its a newbie mistake.
submitted by Psyqo72 to mtred [link] [comments]

I'm getting 0 shares accepted from GUIminer

I'm new to this mining thing. I'm pretty sure I have guiminer set up correctly, but I'm still getting 0 shares. It was working for a little bit before I reformatted my computer, but now it gives me an error and 0 shares. I'm still getting ~250+Mhash. Help please?
2012-02-06 00:11:25: Running command: poclbm.exe username:[email protected]:8337 --device=0 --platform=0 --verbose -v -w128
2012-02-06 00:04:56: Listener for "Default": us.mtred.com:8337 06/02/2012 00:04:56, Unexpected error: 2012-02-06 00:04:57: Listener for "Default": us.mtred.com:8337 06/02/2012 00:04:57, Problems communicating with bitcoin RPC 0 2
submitted by beingmyse1f to mtred [link] [comments]

New to bitcoin mining, just joined MTRED

Hi guys, i just joined MTRED and started to mine.. I use GUIminer atm, when i look at my console i just see
"2012-02-24 18:15:06: Listener for "yaoyao": mine.mtred.com:8337 24/02/2012 18:15:06, Problems communicating with bitcoin RPC 0 2 2012-02-24 18:16:02: Listener for "yaoyao": mine.mtred.com:8337 24/02/2012 18:16:02, Problems communicating with bitcoin RPC 0 2 2012-02-24 18:16:59: Listener for "yaoyao": mine.mtred.com:8337 24/02/2012 18:16:59, Problems communicating with bitcoin RPC 0 2"
all the time. Whats happening, also on www.mtred.com it says my worker has 0 mhs or offline.. Why is this, help please and thanks for great pool :)
submitted by yaoyao1 to mtred [link] [comments]

RPC problems

im having trouble connecting solo or any servers
2011-07-14 16:30:40: Listener for "Untitled": 14/07/2011 16:30:40, Problems communicating with bitcoin RPC 0 2 2011-07-14 16:30:43: Listener for "Untitled": 14/07/2011 16:30:43, Problems communicating with bitcoin RPC 1 2 2011-07-14 16:30:46: Listener for "Untitled": 14/07/2011 16:30:46, Problems communicating with bitcoin RPC 2 2 2011-07-14 16:30:49: Listener for "Untitled": 14/07/2011 16:30:49, Problems communicating with bitcoin RPC 3 2
EDIT: solved, i had to download guiminer version 2011-04-03
i was using the newest and the one before that i tried this older one and it works now
submitted by Stompysteve to BitcoinMining [link] [comments]

Did MtRed just go down?

After mining for a few hours with no problem, I'm suddenly getting a ton of " upstream RPC error" and "Problems communicating with bitcoin RPC". I can connect to Deepbit just fine. Something explode? Someone trip over a cable?
submitted by 54mf to mtred [link] [comments]

First time trying the reddit pool, but this happens

2011-06-23 16:15:36: Listener for "Default": 23/06/2011 16:15:36, Problems communicating with bitcoin RPC
Any ideas on how to fix it so I can mine with redditors?
submitted by hyperhopper to Bitcoin [link] [comments]

Help setting up GUIMiner

So I'm new to the scene and wanted to try out mining. I'm trying GUIMiner on Windows, and I'm not sure that its working. Here is what the log looks like:
2011-06-24 00:28:01: Listener for "Default": 24/06/2011 00:28:01, long poll: new block 0000047bd6482367 2011-06-24 00:29:08: Listener for "Default": 24/06/2011 00:29:08, Problems communicating with bitcoin RPC 2011-06-24 00:30:00: Listener for "Default": 24/06/2011 00:30:00, long poll: new block 00000be9dedbe04d 2011-06-24 00:30:11: Listener for "Default": 24/06/2011 00:30:11, Problems communicating with bitcoin RPC 2011-06-24 00:31:09: Listener for "Default": 24/06/2011 00:31:09, Problems communicating with bitcoin RPC 2011-06-24 00:32:06: Listener for "Default": 24/06/2011 00:32:06, Problems communicating with bitcoin RPC 2011-06-24 00:33:03: Listener for "Default": 24/06/2011 00:33:03, Problems communicating with bitcoin RPC 2011-06-24 00:33:05: Listener for "Default": 24/06/2011 00:33:05, long poll: new block 000004e2357cd0b5 2011-06-24 00:34:00: Listener for "Default": 24/06/2011 00:34:00, Problems communicating with bitcoin RPC 2011-06-24 00:34:57: Listener for "Default": 24/06/2011 00:34:57, Problems communicating with bitcoin RPC 2011-06-24 00:35:54: Listener for "Default": 24/06/2011 00:35:54, Problems communicating with bitcoin RPC 2011-06-24 00:36:50: Listener for "Default": 24/06/2011 00:36:50, Problems communicating with bitcoin RPC 2011-06-24 00:37:47: Listener for "Default": 24/06/2011 00:37:47, Problems communicating with bitcoin RPC 2011-06-24 00:38:45: Listener for "Default": 24/06/2011 00:38:45, Problems communicating with bitcoin RPC 2011-06-24 00:39:43: Listener for "Default": 24/06/2011 00:39:43, Problems communicating with bitcoin RPC 2011-06-24 00:40:40: Listener for "Default": 24/06/2011 00:40:40, Problems communicating with bitcoin RPC 2011-06-24 00:41:37: Listener for "Default": 24/06/2011 00:41:37, Problems communicating with bitcoin RPC
http://i.imgur.com/S7Y3A.jpg
halp
submitted by timwizard to mtred [link] [comments]

What does this error message in GUIMiner mean?

Windows 7, The error messages are as follows:
2012-03-01 20:50:59: Listener for "Silent Video Card": eu.triplemining.com:8344 01/03/2012 20:50:59, Problems communicating with bitcoin RPC 0 2
2012-03-01 20:51:00: Listener for "Silent Video Card": eu.triplemining.com:8344 01/03/2012 20:51:00, Problems communicating with bitcoin RPC 1 2
2012-03-01 20:51:07: Listener for "Silent Video Card": eu.triplemining.com:8344 01/03/2012 20:51:07, Problems communicating with bitcoin RPC 2 2
2012-03-01 20:51:11: Listener for "Silent Video Card": eu.triplemining.com:8344 01/03/2012 20:51:11, Problems communicating with bitcoin RPC 3 2
2012-03-01 20:51:11: Listener for "Silent Video Card": eu.triplemining.com:8344 01/03/2012 20:51:11, No more backup pools left. Using primary and starting over.
Tried Google, got nothing. Thanks!
submitted by zinc55 to Bitcoin [link] [comments]

Cannot connect to Bitcoin RPC

I'd really appreciate some help, I'm running amd64 debian squeeze and I've downloaded the bitcoin client, poclbm, and phoenix. I'm trying to pool mine at https://eclipsemc.com/ and I've used "./poclbm.py -u -p --host=http://us.eclipsemc.com --port=8337 -d 0" which returns "Problems communicating with bitcoin RPC". I also tried "./phoenix.py -u http://:@us.eclipsemc.com:8337 DEVICE=0" and that returns [16/06/2011 17:43:44] Phoenix r101 starting... [16/06/2011 17:43:44] Failed to connect, retrying..." Obviously I've added in my user and password.
Here are the two devices I can use:
[0] AMD Phenom(tm) II X4 955 Processor [1] ATI RV730
And here is my lspci -v:
01:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon >HD 4670] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 2009 Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at d0000000 (64-bit, prefetchable) [size=256M] Memory at fe9e0000 (64-bit, non-prefetchable) [size=64K] I/O ports at c000 [size=256] Expansion ROM at fe9c0000 [disabled] [size=128K] Capabilities: Kernel driver in use: fglrx_pci
If anyone can shine some light on the subject or just guide me in the right direction that would be great, thanks.
submitted by hexabyte to BitcoinMining [link] [comments]

Can someone help me?

My GUIMiner was working fine for about 2 days. I shut down computer and now when i start it back up it won't mine. When i hit start mining it says: Problems communication with bitcoin RPC and No more backup pools left. Using primary and starting over.
submitted by fullofiron44 to mtred [link] [comments]

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

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

https://preview.redd.it/oly12rv9rqq31.png?width=1500&format=png&auto=webp&s=6667e09b78b0edc6dc3b411e5f96bba36f4a6430

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

Encrypted project calendar(October 05, 2019)

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

Encrypted project calendar(October 06, 2019)

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

Encrypted project calendar(October 07, 2019)

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

Encrypted project calendar(October 08, 2019)

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

Encrypted project calendar(October 09, 2019)

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

Encrypted project calendar(October 10, 2019)

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

Encrypted project calendar(October 11, 2019)

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

Encrypted project calendar(October 12, 2019)

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

Encrypted project calendar(October 14, 2019)

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

Encrypted project calendar(October 15, 2019)

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

Encrypted project calendar(October 16, 2019)

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

Encrypted project calendar(October 18, 2019)

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

Encrypted project calendar(October 19, 2019)

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

Encrypted project calendar(October 21, 2019)

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

Encrypted project calendar(October 22, 2019)

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

Encrypted project calendar(October 23, 2019)

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

Encrypted project calendar(October 24, 2019)

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

Encrypted project calendar(October 25, 2019)

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

Encrypted project calendar(October 26, 2019)

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

Encrypted project calendar(October 28, 2019)

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

Encrypted project calendar(October 29, 2019)

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

Encrypted project calendar(October 30, 2019)

MIOTA/IOTA: IOTA (MIOTA) IOTA will host a community event on October 30th at the University of Southern California in Los Angeles on the topic “How to store data on IOTA Tangle.”
https://preview.redd.it/jfxnwvgcrqq31.png?width=473&format=png&auto=webp&s=6adc6ab9f1c8a5f14874041d1e57a6721b8023b3

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

Telegram: https://t.me/Lay126
Twitter:https://twitter.com/mianhuai8
Facebook:https://www.facebook.com/profile.php?id=100022246432745
Reddi:https://www.reddit.com/useliuidaxmn
LinkedIn:https://www.linkedin.com/in/liu-wei-294a12176/
submitted by liuidaxmn to u/liuidaxmn [link] [comments]

Weekly Dev Update #20

THORChain Weekly Dev Update for Week 03–09 Dec 2019

![](https://miro.medium.com/max/3168/1*jxzqLL5vlWDAd6H5pQ-1eA.png)

Overview

The team believe the current bottleneck to THORChain’s decentralisation is the number of nodes that can participate in a single TSS signing ceremony. As the number of participants grows, the complexity becomes exponential. This is in part because THORChain uses a TSS scheme that has no trusted dealer, which is a non-negotiable aspect. The team scoped out two features this week to address this.

Multi-realm Asgard

Instead of a single Asgard with 66 of 99 participating, Asgard can be broken up into different realms, each with a smaller participation number, such as three 22 of 33 realms. This also means that each realm can be rolled at different times, increasing the availability of the network. THORChain has no opinion on where funds are located, they just have to exist and be accounted for in the network. A Multi-realm Asgard does not change any security characteristics of the network, rather it works to shard the funds and increase the scalability. With Multi-realm Asgard, TSS scalability is no longer a concern, instead the upper limit of nodes now becomes a Tendermint scalability issue. Cosmos Hub is working hard to solve this, recently increasing their node count to 125, and with 300 as their long-term target.

TSS Timeout

The trigger to shard Asgard into smaller realms will no longer be a hard-coded number, instead it will be triggered when the key-gen process in a new vault times out after 10 minutes. This means that if the TSS key-generation process for the increased participation number takes too long, it should be sharded. This prevents the network ever generating a committee size with too many members. 10 minutes was chosen as the cutoff due to diminishing returns above that, and a pre-existing shelling point existing on that particular time-point, thanks to Bitcoin.

Trailing Gas Fee

A 1 Rune Fee was hard-coded into THORChain a week ago as the simple solution to a hard problem. The community had a lot of feedback about this, mainly concerns about ease of updating this in future, and they were correct. THORChain must take the governance-minimal approach to all things, and as a result a programmatic solution has been scoped out. The Network Fee will now be twice the 7-day trailing average of gas fees. This will ensure that it always exceeds the expected gas, and drives long-term income into the system. Currently it is global, but it could easily become chain-specific.

Incentive Pendulum

The system is theoretically unsafe when staked assets exceed bonded assets, whether a cartel exists or not. The reason is that a single node could craft an outgoing transaction that spends asset equally to other defecting nodes, and assuming profit-seeking entities, the assumptions around mutually assured destruction no longer hold. While incredibly unlikely to happen, since defecting nodes would need a modified binary to facilitate this transaction and be able to communicate, the system should protect around this edge case. The solution is to disencentivise staking as the system approaches the edge, so that staking rates reduce and the system becomes safe again. The only tool at the system’s disposal is incentives, and the approach is reduce pool rewards and increase bond rewards. This is known as the “Incentive Pendulum”, designed to keep the system at its happy centre; 67% bonded and 33% staked. The Incentive Pendulum also works in the other direction, increasing incentives to stake at high bond rates. The equation is: poolRewards = (y + x) / (y — x), where x = totalStaked, y = totalBonded. * At exactly 50% bonded and 50% staked, pool rewards will be 0%, incentivising bonding. * At 67% bonded and 33% staked, pool rewards will be 33%, the intended amount. * At 100% bonded and 0% staked, pool rewards will be 100%, incentivising staking.

Removal of Hard-coded Constants

The team intend to remove as many constants as possible from the constants.go file, and replace them with programmatic logic. TSS Timeout, Trailing Gas Fees and Churn Heights help solve this. The team will continue the effort.

THORChain

Cosmos was upgraded to the latest version, allowing the team to begin removing uint64 casting and replacing it with BigInt casting which is better when handling large numbers. The team are also in the process of removing float64 from the codebase, which is unsafe when computed on different machines. * [Upgrade] upgrade to cosmos v0.37.4 * [Bug] fix code coverage counter * stabilize smoke test runs * 224-issue fix validator meta keeper * panic on genesis * Add SafeDivision and removes Float * Resolve: Remove Stake Validation * Resolve “Add min bond requirement” * Resolve “ADD: Incentive Pendulum” * 264-issue fix the way how we broadcast tx to binance RPC host * [Add] Slash bond on bond refund * [Bug] Track gas in yggdrasil vaults * 233-issue add stake handler * add 30 sec timeout to wait for binance txs * Work continues to refactor the codebase to be more modular, testable and easier to grok. * [Refactor] Add unit tests to node account keeper * Resolve “[Refactor] Yggdrasil keeper” * Resolve “[Refactor] Vault Data keeper” * [Refactor] pool addresses keeper * 220-issue refactor Reserve Contributor * [Refactor] observer keeper * Resolve “[Refactor] Pool Staker keeper” * [Refactor] Pool keeper * [Refactor] Staker pool keeper * [Refactor] tx in keeper * [Refactor] reserve contributor handler * [Refactor] Rewrite tx in handler, msg, etc * Resolve “[Refactor] handleMsgBond” * Resolve “[Refactor] handleMsgAck” * [Refactor] add mock txout store * [Refactor] create pool address manager interface * [Refactor] create mock validator manager * Resolve “[Refactor] handleMsgLeave” * Resolve “[Refactor] handleMsgAdd” * [Refactor] version handler * refactor-stake unit tests * [Refactor] TxOutStore * 236-issue handler unstake * [Refactor] Breakout TxIn into two handlers * Resolve “[Refactor] handleMsgConfirmNextPoolAddress”

Bifröst Module

Work begins on the feature/bifrostv2 branch, which is a chain-agnostic Bifröst Module that will be verified to work on Binance Chain, Bitcoin, Ethereum prior to mainnet. Monero has also been scoped out, but testing it may not happen prior to mainnet. https://gitlab.com/thorchain/thornode/tree/feature/bifrostv2

Timelines

The team will soon move away from signalling dates for releases, instead will work to signal around completion status of milestones. Whilst ChaosNet seems to be on time for 03 January, much is left to be done: * [ChaosNet] Artificial Ragnarok * [ChaosNet] 1 Day rotations * Add bond reward events * Create pubkeys endpoint * [ChaosNet] Cap staked rune at 600k * Versionize the constants * Emit Validator Events * THORNode Telegram Bot

Community

To keep up to date, please monitor community channels, particularly Telegram and Twitter: Twitter: https://twitter.com/thorchain_org Telegram Community: https://t.me/thorchain_org Telegram Announcements: https://t.me/thorchain Reddit: https://reddit.com/thorchain Github: https://github.com/thorchain Medium: https://medium.com/thorchain
submitted by thorchain_org to THORChain [link] [comments]

Chat_Report.25>2 - XL

[22:12] it's not like I'm going to be offended that someone feels that way [22:12] but it's not healthy to be a dick about it, and that's kind of the only way that I can think to be able to deal with it [22:12] I guess, that's not a bad way to think about it [22:12] if you're having trouble dealing with it [22:12] I guess I just have to accept that I am not an expert on that [22:12] but I do have the most basic understanding of the concept [22:12] and I have always known what a "dissociative" is [22:12] and that they are in fact a distinct psychological state [22:13] I didn't have to google to find out [22:13] and in fact I have been working on a book on dissociative phenomena for a number of years [22:13] you mean you were trying to find out what they were? [22:13] i just finished [22:14] i got the manuscript finished and submitted a copy [22:14] well, the "book" is still on your todo list [22:14] i'm very anxious to publish [22:15] what about the research? are you doing any research on it? [22:15] and yes [22:16] some, but the bulk of my effort is in trying to make sense of it [22:16] what are you doing to help us understand it? [22:16] and i have a blogpost of my own that goes into the background of the phenomenon [22:16] it would be great if you could tell us a little about it [22:16] it sounds as if the phenomenon has something to do with people who have had a life-altering experience [22:17] and that the thing they have experienced is so powerful that it is capable of completely altering a person's personality [22:17] (well, that and the fact that a person who had such an experience could have access to the internet) [22:17] i'm sorry, but why not just tell us about it in full detail, instead of asking me a bunch of question and letting me decide what to ask [22:18] it would be very convenient to you [22:18] if you hadnt decided not to talk about it until after i had. [22:18] if you want to know more, it's quite common for people with this kind of problem to share their stories. [22:18] (i'm not sure if its normal, but i can assure you its not something i wouldn't ever do to any of you) [22:19] so i don't know what you're implying by saying you're uncomfortable with talking about it? [22:19] i'm just saying that i'm not going to force you to talk about it just because you told me it was hard to talk about [22:19] ok. [22:20] so this is it: you must come here with me now [22:20] ok [22:20] and I'll go to the other rooms and meet everyone. [22:20] I want to make this a place for everyone [22:21] ok [22:21] i'll talk to you when i get there [22:21] OK, I need a little more detail [22:22] What's the plan for getting it into the house? [22:22] well i'll let you know when i get there [22:22] Ok, thanks [22:22] i'll be back around 12:30 and ill be there [22:23] I've sent you a PM for the key and I'll be waiting for you to talk to her [22:23] lol [22:23] *key [22:23] ouch [22:24] But that's just me [22:24] You can't just go and do it like that, y'know? [22:24] lol [22:25] but if it's just a matter of asking me nicely, i don't mind [22:25] just send it to me and i'll do it [22:25] if that's what you want [22:25] I've never asked you to do anything but that, and I know you haven't, but, that's my opinion [22:26] I mean, if it helps you out a little bit, maybe I could just... [22:26] Vorpas, that's okay. I mean, I think you're pretty amazing, I do, I do. I just don't know what you want to do with your life. I think I'd like to try and get the people that are in the game to understand the power and the importance of the community. I mean, when you're playing against, when you see a really bad player, you can tell that that player is having fun, that they are having fun playing the game, because they are making a lot of money, and then you can just understand that it would be fun to play, and there would be a lot of money to be made by just playing the game. And I think the players that are playing it, maybe they don't know what's happening, and maybe they have the wrong idea about it. But it's okay, I'm not going to judge them, it's their own opinion and they're free to believe whatever they want to believe. [22:27] But, I'm just gonna leave that part up to you. [22:27] Cool. [22:27] So I'm just gonna be, like, really happy for you, 'cause I know you've been putting a lot of work into this. [22:28] You are doing it so well! [22:28] And I really appreciate that, like, for the last few months, it's been a struggle to stay motivated enough to do this. [22:28] I am a bit concerned about how long this will take. [22:28] I am just going to say this, if I'm going to continue doing this, I want you guys to stay around. [22:29] Well, I would love to keep helping, but I'm not sure what my plans are at the moment. [22:29] If you were to make a donation, that would be fantastic [22:29] You know, the donations are very helpful. I just thought that it might be good to keep track of who donated what. [22:29] Vorpas_Jabwak, I can try to get someone to check if this was indeed you that made the donation? [22:29] Oh, yeah. [22:29] Thanks! [22:29] You've probably never received one before, but if you were, that would be awesome. [22:30] Just wanted to let you know the new version of Mumble is being released and working on the beta channel. [22:31] If you do have the software I'd love to hear some feedback. I have a lot of questions for it. [22:32] I have a lot of questions for it too, but it's a bit complicated so I might not get a chance to do that anytime soon. I'll make sure to get on that when it is ready. [22:33] I'm glad you like it, I know I really do. I love having an easier to use, but powerful, voice chat. [22:34] I'd really like to make some more changes to the system, and try it out as a whole. But right now it's pretty darned good. [22:35] Thanks Jak. :) [22:35] I'll try my best to keep them updated. [22:35] Ok, I'll let you know when I get to them, Jak [22:35] Sorry if I didn't keep up with you guys. [22:36] Haha, sorry. [22:36] I'll see you around, Jak [22:36] *takes off* [22:36] Sup everyone? [22:36] I'm out [22:36] *in [22:37] sup [22:37] Hey! [22:37] So are you guys all there yet? [22:37] :P [22:38] * Turoth sets mode: +b KhaosReigns [22:38] Oh! I thought you all quit on me [22:38] * Turoth sets mode: +b KhaosReigns+ [22:38] So uh, what's my problem? [22:38] I was hoping you'd tell me to stop [22:38] I was so upset [22:38] I'm sorry [22:38] I should have been better [22:39] I didn't mean to startle you [22:39] You've just always made me feel like I could take care of myself [22:39] I guess I didn't realize that it takes a lot of people to keep the lights on [22:40] I'm sorry, I've never been this shy around people [22:40] It's been such a long time [22:41] This whole situation is just a shock [22:41] I'm starting to feel really nervous [22:41] I have to go home now [22:42] Ok [22:42] I'll see you later [22:42] Ohh, bye [22:42] Take care [22:42] Yeah, it's a long way home [22:42] Have a nice night [22:42] Thanks for everything. I had fun. [22:42] night [22:42] I hope you have a good night. [22:42] Have a nice night. [22:42] Thanks. [22:42] Have a good night. [22:42] Good night [22:42] How is everyone? [22:42] I'm fine. [22:42] Tired, but fine. [22:42] Yeah. [22:43] i dont know what happened [22:43] Don't know yet, so I'm trying to get the details. [22:43] I went out to get food [22:43] got a pizza, was eating it when I was interrupted by my girlfriend [22:43] and she was saying she wanted to see me [22:43] i don't even know where i am right now [22:44] so she called me at work this morning and said 'well, i'm sorry i couldn't make it for you today', and i had to tell her 'okay' [22:45] i cant find her or the phone number or anything [22:45] i was just in the car, and she was in the kitchen [22:45] it must of been a while [22:45] i think she was off last night [22:46] that's funny that you would call me like that [22:46] then you should know that she has been off for a while [22:46] she said she was sick, and i think she said she was going to stay home and rest and it wasn't till today that i found out the truth [22:46] yeah it's a real bummer that it was a false alarm [22:46] like i said she could have possibly been sick but wasnt being honest about it [22:46] it is a big bummer that we wasted so much time on it, but it doesn't change that we found her body [22:46] yeah we know how the night went, we just dont know if she was really asleep when the phone rang [22:46] i just wish she would have just told us the truth instead of getting her feelings hurt [22:46] the real question is: why is it a phone? [22:46] that's all i got [22:46] so that's it [22:46] yeah and she's got to go find out if she's pregnant [22:46] and i guess there's no point in trying to hide the pregnancy [22:46] she said it was just a few days ago [22:46] wait what [22:46] maybe her parents are going to find it [22:46] ok [22:46] maybe if her parents find out she's pregnant [22:46] they'll just throw you out [22:46] they will [22:47] why do you think she was crying? [22:47] well, I mean, I know it's weird but [22:47] no, you're right [22:47] I mean, it was pretty strange [22:47] she just seemed, well [22:47] I don't think she could have known the guy or not [22:47] there's been plenty of reports of people getting "paedo" on the site [22:47] so it could have just been that her brain just caught on [22:47] like that one guy who was arrested last year for having a lot of chatroom porn [22:47] which is like a whole different thing [22:48] and it just happened to be in that section that she kept checking [22:48] yeah [22:48] like it's not like she has this huge fucking file of porn on her computer [22:48] so if it happens to be in one place, it's not like she's a big fucking voyeur [22:49] but still, she was watching the entire thing [22:49] yes, and that is probably why the guy stopped her [22:49] I can see your point of view [22:50] and it was also in that section that she just kept checking [22:50] yes, and I can say that she just seemed so interested in the guy that she wouldn't mind if he was watching [22:50] and that's not exactly the case with me either [22:50] but, if she's only interested in other men, then she's obviously gay [22:51] which is just something to remember [22:51] and she's so smart, but I can't see her getting on with me [22:51] she has a crush on me, but I don't even know where to start [22:52] I was at a party in NY, and someone I knew was talking to her, and they had been flirting. I didn't get a chance to respond, but I am a nice guy. She said she didn't want to talk about it any more. I am a nice guy, and I know that flirting is bad, but I also know that I like her and I think that there's a chance that it could go somewhere. I want to have a relationship with her, I don't really know where to start [22:52] you'd have to ask her yourself [22:52] but it seems like you don't have to [22:52] but if that's your only point she can't really say something else... [22:52] i think if you were to say you didn't want to have sex with her, you would lose her... [22:52] i'm not even really interested in that right now [22:53] it just seems like she wants to have sex with you [22:53] and is hoping that you'll say yes [22:53] i guess so... [22:53] but she doesn't seem to be trying to win your votes [22:53] maybe she's just trying to piss you off [22:54] and you don't have the time to argue with her [22:54] the internet is a bitch. [22:54] but i know she's just trying to be funny [22:54] and to make a point [22:54] so why can't i? [22:54] yeah [22:54] what do you mean? [22:54] jalockk: i've never seen a single one of these people [22:54] but i see them every day [22:54] and they say the same shit [22:54] we don't like the idea of them being taken out because they are not the ones we really are against [22:54] well i don't think we need to be very big to do that [22:54] but they are a part of it [22:55] the people that dont like us [22:55] the people that are behind all this [22:55] or just the people [22:55] not the people [22:55] it's the people that don't have an opinion [22:56] we should never let our ignorance define us [22:56] well we're doing it now [22:56] and it's not even funny [22:56] it's just sad [22:56] no it's a serious problem [22:56] it's not funny [22:56] and the truth is sadder [22:56] i don't understand why he hates himself so much [22:56] is it because of the death [22:56] or the lies he told [22:56] that's what im trying to figure out too [22:57] not that there is an obvious answer to why he does what he does [22:57] i think he is a pretty shitty person [22:57] the lies hurt more [22:57] i really really wish i could understand [22:58] that's why i'm here to explain the way out [22:58] if i explain it to you in words [22:58] well i don't know you [22:58] i have to explain it to you in a way that makes sense to you [22:58] in english [22:58] and that's how [22:58] this whole thing starts with a picture of a woman [22:58] holding up a phone with the words "HELLO" on the screen [22:58] it's a picture of me [22:58] It's a pic of me in a hat [22:58] and i'm in the hat [22:58] which isnt me [22:58] i'm the one with the hat [22:59] i wear a hat to hide my face [22:59] and when i say this i don't really say "i'm the hat" [22:59] i say "i'm the hat" [22:59] oh okay [22:59] ok let me get this straight [22:59] if we're talking about the "why" [22:59] what the actual, fucking, fuck [22:59] why did she do it [22:59] the "when" part I'm not clear about [22:59] i'd assume that's the part we're discussing [22:59] ok i'm getting out of this [22:59] but yeah the "what" [22:59] yeah [22:59] and it seems like the "how" [22:59] isnt really a big deal [22:59] i think it is [22:59] the fact that we all agree on what it is [22:59] and are people who say its a big deal really saying it on the op? or is it on the op, and people who say its a big deal are just assholes? [22:59] we're pretty fucking certain it's not a big deal [22:59] if you're not convinced [22:59] please say so in the thread [22:59] i'd love to hear your arguments [22:59] the op is just a big deal, it is a huge deal, we've done the math, and there is no downside [22:59] we've actually spent the last 2 days talking about it [22:59] it doesn't really have any consequences on us, as we won't do anything stupid [22:59] we'd be better off not having it in the first place [22:59] it doesn't really matter [22:59] I know I'm a bit biased but... this whole thing feels like it's been set up to be solved by trolls [22:59] not to mention that we can already see a lot of the stuff they are talking about, they just don't want to talk about it [22:59] it's not like they would go back to it and say "we got this, so why don't you shut up!" [22:59] It's frustrating to see them try and keep this open... but it's a shame to see what happens when they fail. [22:59] I love how it seems like the more they try to keep it secret, the more they are forced to keep it open [22:59] :O [23:00] well we don't know yet what they have planned for the next phase but there's a lot of work to be done [23:00] no one knows what we'll be doing now, so if we do everything right, we could actually end up with some more power [23:00] i'm not saying we'll get that, we'll have to wait and see [23:00] maybe i'm just a bit optimistic [23:00] or maybe i'm just stupid? [23:01] i dunno i don't care anymore [23:01] just wait it out [23:01] no time to waste [23:01] let them make it as easy as possible [23:01] and keep an eye on what they say next [23:01] well that could mean some kind of delay [23:01] like they are going to push it out [23:01] well, that's their prerogative [23:01] what they said a month ago is what they're saying now? [23:01] Ok, I'm gonna leave this here: http://en.wikipedia.org/wiki/Woot\_com [23:01] but I can't find the link right now. :( [23:01] it's been posted to the website of the US government [23:01] so you know it's legit [23:02] oh. Ok. [23:02] so it's legit [23:02] ok. [23:02] So, we're not really at the point of doing the whole, "we have a solution" thing, so much as a "we have a general idea" thing. [23:03] i think that's what we're going for [23:03] the problem, in my experience, is that it's hard for people to really figure out what you're talking about. I would assume that with a lot of the work that's going on there are some people who are really good at solving it. I'm not. [23:04] i mean, it is sort of in the realm of "people" [23:04] that we've been able to make progress on this, so i am assuming you have done a lot of that work? [23:04] i would have to ask someone else how they are doing it [23:05] in terms of the algorithms they use [23:05] or other tools [23:06] http://bitinfocharts.com/blocksize-and-bitcoin-future-chart/ [23:06] but i don't know how you guys did it in a way that is also practical [23:06] no problem. it's been done. [23:06] just don't expect anyone to do it for you [23:07] i'll have to ask you that one [23:07] if you have a better idea please post it here and we'll discuss it [23:07] but if we don't have a better idea then we don't know what you're talking about [23:08] it's not our fault they are doing it [23:08] they do it to us [23:08] we don't have any other solution [23:08] but they have access to your wallet [23:09] you are paying for access to it [23:09] so they are getting access [23:09] you are paying to keep their access to your wallet [23:10] I am paying to keep your access to your wallet [23:10] they are making you do it [23:10] i am paying them to keep access to my wallet [23:10] that is what i have been told to do [23:10] what i was told to do [23:10] i am also paying them for this access [23:10] I am not paying to keep access to my wallet for them [23:11] I am paying them for this access [23:11] to mine in their account for them [23:12] well, that was fun [23:12] oh, that's too bad [23:12] it's all for you [23:12] you are mining it for them [23:12] so much for that [23:12] but then you are the victim of a scam, not me [23:13] oh, ok [23:13] it's a good thing you are aware now, because that is a great way to get scammed [23:13] so what's up? [23:14] ok [23:14] we've been looking for you for a while now and we can't find you. [23:14] ok. so what's up? [23:15] the last time you were on IRC we started doing our own investigation and you didn't know where you were or how long you'd been gone [23:15] so we thought that since you weren't there anymore that it had to be a scam [23:15] which it is [23:15] http://www.youtube.com/watch?v=h0bzvq8Fx7Y [23:15] yeah. but it doesnt tell you that [23:15] you gotta ask [23:15] you got that right [23:16] alright. let me see if I can find something similar [23:16] https://www.youtube.com/watch?v=nUZpwWg1g\_s [23:16] http://www.youtube.com/watch?v=pFwX4jJYqhI [23:16] i have a different one [23:16] http://www.youtube.com/watch?v=h\_h2rK4V7ZM [23:16] it is shorter [23:16] it has less information [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http://www.youtube.com/watch?v=DYpq6H2jkZg [23:17] http ://www.youtube.com [23:17] http://www.youtube.com [23:17] http://www.youtube.com [23:17] ok I have been listening [23:18] let me hear your response to the question "why are you talking on the radio?" [23:18] "The answer to that is because I was just trying to communicate with the community" [23:18] why do you think it's a good idea to try to communicate with the community? [23:18] you don't need to ask, we're going to have a drink [23:18] let me get you something to drink [23:18] i will be back later [23:18] in like 2 mins [23:18] can you hear me? [23:18] yes, I can hear you [23:18] are you a bot? [23:18] no, i am human [23:19] oh [23:19] good to know [23:19] you're just very very drunk, i guess [23:19] just go to sleep [23:20] you just have to go to sleep [23:20] and it'll be over by the morning [23:20] i'll wait [23:21] but it was only a few hours ago [23:21] and i said it wouldn't be [23:21] so i'm guessing you can't help it [23:21] so is it over? [23:21] not sure if you can help it or not, but if you have any questions or suggestions, do send them to me [23:22] but yeah, there is no immediate threat at all [23:22] but i dont know what to do at the moment, maybe i should move everything to another server [23:22] but i have the code and the rpc server [23:22] you can do that? [23:22] yeah, just let me know what you want [23:22] okay, how do i run rpc from my localhost? [23:22] just open up a terminal and run "rpcuser -i 127.0.0.1" [23:22] okay [23:22] let's go back to maint [23:22] I'm going to add another option to run the wallet (wallet.conf) as a non root user [23:22] I'm going to add rpcuser as an option, and rpcpassword as a second option [23:22] and then run as root [23:23] okay, so what do i want the output of this command to be [23:23] the output should be something like "1" [23:23] what should i put in the command? [23:23] for now, i'll just type it out [23:23] rpcuser=myuser rpcpassword=mypassword [23:23] run_in_remote.sh --port=21 --listen=127.0.0.1:2222 [23:23] you should be able to type that in [23:23] and it should go through ok. you should see something like this: [23:23] [00:11] [23:21] [00:20] [23:23] what do i do to make the next post more visible? [23:23] can someone send a screenshot of the reddit post to me? [23:23] @emmaw [23:23] i can give you my address in case you want to send something there [23:23] you're welcome [23:23] well im going to have to ask the mod team that question now [23:23] thanks for the offer, we'll think about it [23:23] :) [23:23] i'll give you the link soon, also [23:23] but please don't PM me about that :) [23:24] sure [23:24] i'll leave it with you [23:24] but i'll check it again [23:24] later [23:25] so is this the one with the red pill? [23:25] or redpilled? [23:25] redpilled [23:25] redpilled [23:25] ok [23:25] thanks [23:25] I got the link [23:25] yeah [23:25] this is a very big deal [23:25] I'm in a hurry, so I can't see the link, but what you're doing is a lot more powerful than most of what I've ever heard before [23:26] http://www.youtube.com/watch?v=Hjf7hKQ6uQg [23:26] that's a pretty long video [23:26] yeah [23:26] there's lots of cool stuff in there, too [23:26] it has a nice flow to it, too [23:26] so, you have to remember: don't focus on the structure, focus on the content [23:27] i see [23:27] not sure if thats just me though [23:27] its a good thing to have [23:27] not sure why the devs don't do it, but there are some good reasons [23:27] yeah i got your point [23:27] im happy to make it easy for you [23:27] and for other devs to do it as well [23:27] (at least a few of the devs are here to see this) [23:27] we could even get a group of devs to go talk to the press and try to have the topic in a few of the big gaming sites [23:28] this could be a great way to get the game out and to everyone else [23:28] and then we can move onto the next thing [23:28] if this is successful I think we can even get some of the smaller ones to try it [23:28] also if any of the other big ones do it this will get them in on the process
submitted by ShadowWolf525 to WeirdGeneratedStories [link] [comments]

With all of the hullabaloo about a thin Dogecoin wallet, specifically naming Electrum, I went and analyzed both Electrum and the official P2P protocol's own thin-client support. I think I might have found a really big problem with them.

…and the thing that’s really got my jimmies rustled is how obvious the problem appears on the surface, and how I can’t find anyone else talking about it. So if you all don’t mind, I’ll go ahead and describe what I think could be the achilles heel of contemporary crypto currency thin clients. I'll be making some really strong assertions, but if anyone has any information that contradicts them, please share!
EDIT: By request from jdk, an abstract of sorts:
Light cryptocurrency wallets take absence of evidence as evidence of absence. Since they cannot verify that the nodes they are talking to have told them the full truth, it's possible that they will miss some incoming transactions.
I describe three attacks:
1. The simplest one don't tell the client about certain transactions. Because bitcoinj ignores block headers it has already seen, this attack is super effective! against it. Electrum, too, so long as all the nodes it's connected to all agree to not tell it. Once someone does tell it about a past transaction, it verifies it, and then adds it to your wallet. Unfortunately, this can be used to facilitate the third attack.
2. (This only applies to Electrum) A slightly more complicated attack has the attack nodes refuse to acknowledge a single outgoing transaction. Because Electrum always uses the oldest transactions to create new transactions, and because it takes absence of evidence as evidence of absence, you can freeze a user's wallet for as long as they are connected to you, or if they don't inspect older blocks. But, again, inspecting older blocks opens you up to the third attack.
3. A merchant and an attacker can conspire against you to trick you into sending your coins twice. They do this by running the second attack, then back-feeding older transactions so your client will attempt to spend those first. This will work as long as you, the user, try to re-initiate the transaction that supposedly failed.
If you haven’t already read the Bitcoin White Paper, I suggest you go ahead and read it, specifically Section 8 on Simplified Payment Verification. I found it to be fairly straightforward, and it should give you enough background to understand what’s going on. I'm also discussing Electrum and bitcoinj, the latter being a specific example of a client which, by default, relies on Simplified Payment Verification, henceforth known as SPV.
When people speak of "thin" clients, they are referring to clients that do not download all of the transactions in a block along with the block headers. Instead, they only download some of them. Because a block containing transactions links to its transactions by way of a Merkle tree, it is possible to omit a majority of transactions, yet still verify that the ones given were indeed present in the block. It is this property of Merkle trees that allows SPV to be possible.
Electrum came about just when the Bitcoin blockchain became too large for most people to stomach, a lot like what is happening with the Dogecoin blockchain now. The mechanics of SPV had been known in the community for as long as the white paper was released publicly, but the core protocol did not directly support it. Electrum was a series of cute, workable hacks that resulted in an SPV client, but also a client-server architecture and a completely different RPC protocol. At the time, it was necessary in order to receive the filtered transaction notifications necessary to efficiently implement SPV. However, the core Bitcoin Peer-to-Peer protocol now supports the capability of notifying peer nodes of what kinds of transactions of which you wish to be notified. The peers will always respond with blockchain headers, and in the event that any interesting transactions appear to be found, the Merkle branches of those transactions. The client then filters out the false positives (in order to efficiently implement this, the protocol uses a data structure called a Bloom Filter to encode the interesting wallets in a compact manner. It is susceptible to false positives, but that's OK, because you can safely ignore them) and verifies that the transactions sent were actually part of the block by rebuilding the Merkle root and comparing it to that of the block.
This is all well and good from an efficiency standpoint, but any sort of *coin being a type of currency, and thus demanding a high standard of security, I hold some gripes about both Electrum in particular and SPV in general that I feel make them unsuitable for the purposes for which they are currently being used.
The Electrum client begins its connection to the Bitcoin network through a series of hard-coded individual servers. There is a mechanism for describing more peers through IRC; the channels for which are provided by the servers contacted at start-up. I fear that this design empowers both the authors of the client and the owners of the seed servers far too much. In collusion, administrators of the seed servers could elect to not run IRC channels at all, or, alternatively, moderate out any servers from non-colluding parties. This could be used to facilitate something disastrous, particularly what I am about to describe.
In general, SPV provides excellent protection from false positives. Any transaction received with a Merkle branch must continue to hash to the proper child value until the Merkle root is reached. If the Merkle root is linked to a trusted block in the blockchain, its existence in the network is proved. But, it is computationally infeasible to protect from false negatives in a SPV scheme. All the peers need to do is refuse to pass on certain transactions. The client will be none the wiser for it, because the client never knew about them in the first place.
This can obviously be used to facilitate an “output garnishing” attack: simply ignore certain transactions outputting to a certain wallet when responding to the client. The client will not be able to see that there are more unspent outputs to its wallets, because he trusts and relies on his peers to do that instead.
"Output garnishing" can be reworked into a "wallet freezing" attack that completely locks the client out of the network. The attacking node may elect to pass an outgoing transaction to the network, but fail to relay the transaction’s status to the client. The client will believe that the transaction was unsuccessful, and because both Electrum and bitcoinjEDIT: bitcoinj marks outgoing transactions as "pending" and won't double-spend them deterministically attempts to spend the oldest transactions first, any further attempts to create transactions will be seen as a double-spend attempt by the network. As long as the client is only communicating with the attacking nodes, he is incapable of making any further purchases.
In Electrum, the solution may be trivial. Download the client source, modify the seed server list to be more trustworthy. Still, that there is now explicit trust in the network nodes is a far cry from the security of the original protocol design.
In bitcoinj, there is no solution. In fact, an attacker only needs to control one node; bitcoinj simply ignores all further communication about valid blocks it has seen only once before! The comments in the bitcoinj source code seem to suggest this was a performance optimization. However, not doing this would open bitcoinj up to another type of attack, to which Electrum is already vulnerable: a “double-purchasing” attack.
EDIT: The preceding paragraph doesn't completely apply as per the previous edit, but I'm leaving it in for consideration with regards to the first attack. Bitcoinj still ignores older blocks, even if they have new, relevant transactions in them.
Suppose a merchant M is in collusion with an attacker A who runs a series of nodes N0…Nn. Suppose also, that a client C, using a wallet Wc, wishes to purchase from M, using a wallet Wm, both of which are known to M and subsequently A.
A constructs N0…Nn such that certain transactions to Wc are silently ignored (call them Ti); valid in the network but never delivered to C. A waits until there are no more unspent transactions to Wc not in Ti older than some T in Ti. Upon an attempted transaction (Wc -> Wm)0, Nk with 0 <= k <= n sends the transaction to other peers but does not respond to C. Instead, Nk responds with some Ts0…Tsn in Ti such that the sum of outputs in Ts0…Tsn to Wc is greater than or equal to the outputs of (Wc -> Wm)0. C accepts these Ts0…Tsn. An unaware user may elect to begin a new transaction (Wc -> Wm)1 in lieu of a response regarding (Wc -> Wm)0. Because (Wc -> Wm)1 will use as inputs from unspent transaction outputs not used in (Wc -> Wm)0, indeed not yet used at all, the network will accept both transactions as valid! A may elect to continue this process for any (Wc -> Wm)n so long as the sum of all Tin in Ti is sufficient to cover the costs of all Tout in (Wc -> Wm)0…(Wc -> Wm)n. A has effectively coerced C into double-purchasing.
Even if Electrum and bitcoinj randomly chose unspent outputs as inputs for the new transaction, as does the reference Bitcoin client, the probability that such an attack could succeed at least once is directly proportional to the input activity of the target wallet, and the attacker would only need to withhold that particular outgoing transaction to succeed!
I’m looking for some peer review on this. If these scenarios are possible, the proliferation of SPV clients for Bitcoin (and perhaps in the future, Dogecoin) could make an adversary’s life very easy! Again, constructive hole-poking and educative discussion weakening this hypothesis are very, very welcome.
EDIT: And I'm all out of characters! More edits will end up in the comments.
submitted by chia_pet to dogecoin [link] [comments]

gRPC LND Python Problem

I am currently struggling to work myself through gRPC with my LND Node using Python.
I've set everything up using this tutorial.
Getinfo works as described in the tutorial.
Now I created an invoice with Starblocks but struggle to get my head around how to satisfy it using a script.
My script:
import rpc_pb2 as ln import rpc_pb2_grpc as lnrpc import grpc import os # Due to updated ECDSA generated tls.cert we need to let gprc know that # we need to use that cipher suite otherwise there will be a handhsake # error when we communicate with the lnd rpc server. os.environ["GRPC_SSL_CIPHER_SUITES"] = 'HIGH+ECDSA' # Lnd cert is at ~/.lnd/tls.cert on Linux and # ~/Library/Application Support/Lnd/tls.cert on Mac cert = open(os.path.expanduser('/home/pi/.lnd/tls.cert'), 'rb').read() creds = grpc.ssl_channel_credentials(cert) channel = grpc.secure_channel('localhost:10009', creds) stub = lnrpc.LightningStub(channel) import codecs # Lnd admin macaroon is at ~/.lnd/data/chain/bitcoin/simnet/admin.macaroon on Linux and # ~/Library/Application Support/Lnd/data/chain/bitcoin/simnet/admin.macaroon on Mac with open(os.path.expanduser('/home/bitcoin/.lnd/data/chain/bitcoin/testnet/invoice.macaroon'), 'rb') as f: macaroon_bytes = f.read() macaroon = codecs.encode(macaroon_bytes, 'hex') metadata = [('macaroon',macaroon)] invoice_response = stub.AddInvoice("lnt...",metadata=metadata) payment_request = invoice_response.payment_request for payment in stub.SendPayment(payment_request): print(payment) 
Note that I've shorted the invoice code (first parameter) from Starblocks in the function "AddInvoice"

I am totally lost right now as I work myself through this file and this documentation to see which functions are available and expect which parameters. Someone stated that I would have to use the macaroon in "AddInvoice" and I don't even know why or what that is.

I try to setup two nodes in the future to create and pay invoices of each other to stresstest the speed of routing and the payment itself. I know this has been done before but I need that data from my own test for an exam.
Sorry to bother you and I would read myself into it but the data is due in two days and the stress is not helping me understand.
(Damn procrastination)
Thanks guys!
€: sendpayment via shell is no problem at all!
submitted by snt1991 to lightningnetwork [link] [comments]

Jaxx - Monero Integration Update #3

Hey Monero Community, Anthony from Jaxx here with another update.
For those of you that don't know we at Decentral recently joined the Monero community and are working on integrating Monero to our Jaxx Wallet. Jaxx is a free multi-token, multi-platform light wallet that's dedicated to uniting the crypto-ecosystem and providing an interface to Blockchain tech (in a similar way the browser unleashed the power of the internet to the masses). Among other things, it is the goal of Jaxx and Decentral to allow people to be in full control of their digital lives. All keys in Jaxx are held client-side and a single 12-word backup phrase allows for the derivation of the keys to all tokens we support, and will ever support. Also, all our products are design and user experience driven as we make stuff for the masses, so that people (like my non-technical Dad) can have a great experience.
One thing I’d like everyone to remember and keep in mind is that we’re still very new to the community and much of the history of the project is not clear to us still. As you read the rest of my message, please keep this in mind and know that we are not trying to call anyone out or cause conflict in the Monero community. We just want to see Monero thrive.
Here we go.
Monero integration has been on a radar for over a year and over the past weeks and months we dove headfirst into XMR and have since spent more than 400 hours working on this particular integration. During this time we have gained massive knowledge on the inner workings of the Monero protocol, and of the Monero development ecosystem. Our goal is to provide a lightweight (~3 meg) solution for the Monero community that will allow them to manage, send and receive XMR on pretty much any platform or device.
As a result of working to integrate other projects, our 3 years of experience developing wallets, through my experience as a founder of Ethereum, as an early Bitcoin adopter and community builder, and via extensive research and code creation we’ve done for Monero, we believe to have determined the critical issues that are leading to problems with Monero growth and that these problems are hindering the adoption and success of the Monero ecosystem.
As such we are putting a call out for support from the Monero development community to help us break through these problems. We are confident that if these roadblocks can be bypassed, Monero has a great chance to flourish. We believe that unless solved, these issues will greatly hinder Monero's ability to compete with projects that have similar features
Before I get into the issues I want to explain and give some background on how our integration process usually works when we tackle a new project, then I'll explain how things are currently working with the Monero Integration.
Our goal is to implement an XMR lightweight wallet in Jaxx that connects with a high level cryptocurrency API. In most cases (with our previous integrations) there is an existing client library to use for the particular token in question. We have a full stack blockchain development team of 9 that can go from modifying cryptocurrencies nodes to providing high level APIs. We first start any project by making feasibility analysis to check how easy or difficult is to integrate a light wallet with a cryptocurrency. When we see critical unsolved issues or roadblocks, we talk with the specific cryptocurrency team as early as possible. If they have the resources they help us to mitigate those issues. When they don’t have the resources to make the necessary changes, we take the responsibility for these tasks but they provide some guidance based on their expertise.
That's how things normally work. Here's how it's working with Monero.
We researched the feasibility of providing a light wallet for Monero and found the main challenges to be:
  1. Non-existing lightweight client library support (for a project as old as Monero its peculiar no dev has done this)
  2. We would have to implement support for anonymization features.
  3. There are RPC (Remote Procedure Calls) API Limitations that would require changes in the Monero daemon
Here's what we've been able to accomplish so far:
  1. Finish a Monero javascript client library
  2. Use the same approach as MyMonero re anonymization (e.g. persisting the viewkeys)
  3. Modify Monero Core to support a lightweight wallet.
Currently we are developing an API on top of monerod to provide additional web services.
Now here's the problem.
We have realized critical issues that are difficult to solve at the RPC API level without the development community's support. Basically we would like to get the global indexes in the transaction output via the RPC API, which are required for sending transactions, but when we call methods such as gettransactions we don't receive this information. We also try to call the *.bin RPC methods as well but they return error code HTTP 404. Ok fine. If this method is not supported in monerod there are two alternatives: 1) either the core team can add them to make it easier for the entire community to build apps on top of Monero, or 2) we can modify the Monero node itself to add support for new RPC methods required for building applications (like the Jaxx wallet or any other wallet).
The problem with us choosing the second method is the amount of time it's going to take us to "instrument" the code is unknown as this would be an intensive research project by people who didn't work on developing any part of Monero. Like a needle in a haystack. Also, should we have to directly hook into the code it could become easily broken in the future as new code gets pushed by the Monero core team. If (and that's a big if) we were to go down this route of instrumenting the code we would need a commitment from the Monero core team to accept the code push and to continue supporting it in the main branch.
Without either of these two options being completed it means that Monero as it is isn't able to bring enough information outside of the node in order to develop a full wallet.
As mentioned in previous update posts, we'd like to thank Fluffypony for providing us with assistance with the integration. But we need more help than he's been able or willing to provide. The issue is that his help has been limited as although he is a main contributor to Monero, he also owns MyMonero and has a profit incentive not to give away his "secret sauce" on the back-end. You see, MyMonero hooks right into the code and this coupled with him being one of the few main contributors on the Monero Github gives MyMonero an upper hand against other projects trying to create similar services.
We understand and accept Fluffypony's motives and situation. He's put a ton or resources and effort into Monero and into MyMonero. What we'd like to do is call on anyone else who may be able to help to break through these barriers. Please email me at anthonyATdecentral.ca if you would like to join our slack channel and see if we can crack the problem’s we’ve identified and are facing. We fear if we don't have more assistance from core Monero devs to act as guides we (or anyone else for that matter) will not be able to bring the products and services necessary for the Monero community to flourish.
Have a great weekend all!
Anthony Diiorio
CEO & Founder
Decentral / jaxx.io
EDIT - We are re-evaluating our transparency and use of Reddit to communicate with the Monero community. The amount of venomous comments and lack of support in response to said comments are really disheartening and don't inspire us to continue working on the Monero integration...but maybe that's what some of those commenting want.
EDIT - After internal discussions we've decided not to use Reddit any more to discuss our Monero plans. Turning out to be more detrimental to our team then its worth. Moving the discussions fully to our Slack channel and our other social media avenues.
submitted by Jaxx_adiiorio to Monero [link] [comments]

IRC Log from Ravencoin Open Developer Meeting - Aug 24, 2018

[14:05] <@wolfsokta> Hello Everybody, sorry we're a bit late getting started
[14:05] == block_338778 [[email protected]/web/freenode/ip.72.214.222.226] has joined #ravencoin-dev
[14:06] <@wolfsokta> Here are the topics we would like to cover today • 2.0.4 Need to upgrade - What we have done to communicate to the community • Unique Assets • iOS Wallet • General Q&A
[14:06] == Chatturga changed the topic of #ravencoin-dev to: 2.0.4 Need to upgrade - What we have done to communicate to the community • Unique Assets • iOS Wallet • General Q&A
[14:06] <@wolfsokta> Daben, could you mention what we have done to communicate the need for the 2.0.4 upgrade?
[14:07] == hwhwhsushwban [[email protected]/web/freenode/ip.172.58.37.35] has joined #ravencoin-dev
[14:07] <@wolfsokta> Others here are free to chime in where they saw the message first.
[14:07] == hwhwhsushwban [[email protected]/web/freenode/ip.172.58.37.35] has quit [Client Quit]
[14:08] Whats up bois
[14:08] hi everyone
[14:08] hi hi
[14:08] <@wolfsokta> Discussing the 2.0.4 update and the need to upgrade.
[14:08] <@Chatturga> Sure. As most of you are aware, the community has been expressing concerns with the difficulty oscillations, and were asking that something be done to the difficulty retargeting. Many people submitted suggestions, and the devs decided to implement DGW.
[14:09] <@Tron> I wrote up a short description of why we're moving to a new difficulty adjustment. https://medium.com/@tronblack/ravencoin-dark-gravity-wave-1da0a71657f7
[14:09] <@Chatturga> I have made posts on discord, telegram, bitcointalk, reddit, and ravencointalk.org from testnet stages through current.
[14:10] <@Chatturga> If there are any other channels that can reach a large number of community members, I would love to have more.
[14:10] <@wolfsokta> Thanks Tron, that hasn't been shared to the community at large yet, but folks feel free to share it.
[14:10] When was this decision made and by whom and how?
[14:10] <@Chatturga> I have also communicated with the pool operators and exchanges about the update. Of all of the current pools, only 2 have not yet updated versions.
[14:11] <@wolfsokta> The decision was made by the developers through ongoing requests for weeks made by the community.
[14:12] <@wolfsokta> Evidence was provided by the community of the damages that could be caused to projects when the wild swings continue.
[14:12] So was there a meeting or vote? How can people get invited
[14:12] <@Tron> It was also informed by my conversations with some miners that recommended that we make the change before the coin died. They witnessed similar oscillations from which other coins never recovered.
[14:13] only two pools left to upgrade is good, what about the exchanges? Any word on how many of those have/have not upgraded?
[14:13] <@wolfsokta> We talked about here in our last meeting Bruce_. All attendees were asked if they had any questions or concerns.
[14:13] == blondfrogs [[email protected]/web/freenode/ip.185.245.87.219] has joined #ravencoin-dev
[14:13] == roshii [[email protected]/web/freenode/ip.41.251.25.100] has joined #ravencoin-dev
[14:13] sup roshii long time no see
[14:14] <@Chatturga> Bittrex, Cryptopia, and IDCM have all either updated or have announced their intent to update.
[14:14] == wjcgiwgu283ik3cj [[email protected]/web/freenode/ip.172.58.37.35] has joined #ravencoin-dev
[14:15] sup russki
[14:15] what's the status here?
[14:15] I don’t think that was at all clear from the last dev meeting
[14:15] I can’t be the only person who didn’t understand it
[14:15] <@wolfsokta> Are there any suggestions on how to communicate the need to upgrade even further? I am concerned that others might also not understand.
[14:17] I’m not sold on the benefit and don’t understand the need for a hard fork — I think it’s a bad precedent to simply go rally exchanges to support a hard fork with little to no discussion
[14:17] so just to note, the exchanges not listed as being upgraded or have announced their intention to upgrade include: qbtc, upbit, and cryptobridge (all with over $40k usd volume past 24 hours according to coinmarketcap)
[14:18] <@wolfsokta> I don't agree that there was little or no discussion at all.
[14:19] <@wolfsokta> Looking back at our meeting notes from two weeks ago "fork" was specifically asked about by BrianMCT.
[14:19] If individual devs have the power to simple decide to do something as drastic as a hard fork and can get exchanges and miners to do it that’s got a lot of issues with centralization
[14:19] <@wolfsokta> It had been implemented on testnet by then and discussed in the community for several weeks before that.
[14:19] == under [[email protected]/web/freenode/ip.72.200.168.56] has joined #ravencoin-dev
[14:19] howdy
[14:19] Everything I’ve seen has been related to the asset layer
[14:19] I have to agree with Bruce_, though I wasn't able to join the last meeting here. That said I support the fork
[14:20] Which devs made this decision to do a fork and how was it communicated?
[14:20] well mostly the community made the decision
[14:20] Consensus on a change is the heart of bitcoin development and I believe the devs have done a great job building that consensus
[14:20] a lot of miners were in uproar about the situation
[14:20] <@wolfsokta> All of the devs were supporting the changes. It wasn't done in isolation at all.
[14:21] This topic has been a huge discussion point within the RVN mining community for quite some time
[14:21] the community and miners have been having issues with the way diff is adjusted for quite some time now
[14:21] Sure I’m well aware of that -
[14:21] Not sold on the benefits of having difficulty crippled by rented hashpower?
[14:21] The community saw a problem. The devs got together and talked about a solution and implemented a solution
[14:21] I’m active in the community
[14:22] So well aware of the discussions on DGW etc
[14:22] Hard fork as a solution to a problem community had with rented hashpower (nicehash!!) sounds like the perfect decentralized scenario!
[14:23] hard forks are very dangerous
[14:23] mining parties in difficulty drops are too
[14:23] <@wolfsokta> Agreed, we want to keep them to an absolute minimum.
[14:23] But miners motivation it’s the main vote
[14:24] What would it take to convince you that constantly going from 4 Th/s to 500 Gh/s every week is worse for the long term health of the coin than the risk of a hard fork to fix it?
[14:24] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has quit [Ping timeout: 252 seconds]
[14:24] This hardfork does include the asset layer right? if so why is it being delayed in implementation?
[14:24] <@wolfsokta> Come back Tron!
[14:24] coudl it have been implement through bip9 voting?
[14:24] also hard fork is activated by the community! that's a vote thing!
[14:24] @mrsushi to give people time to upgrade their wallet
[14:25] @under, it would be much hard to keep consensus with a bip9 change
[14:25] <@wolfsokta> We investigated that closely Under.
[14:25] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has joined #ravencoin-dev
[14:25] <@wolfsokta> See Tron's post for more details about that.
[14:25] <@spyder_> Hi Tron
[14:25] <@wolfsokta> https://medium.com/@tronblack/ravencoin-dark-gravity-wave-1da0a71657f7
[14:25] Sorry about that. Computer went to sleep.
[14:26] I'm wrong
[14:26] 2 cents. the release deadline of october 31st puts a bit of strain on getting code shipped. (duh). but fixing daa was important to the current health of the coin, and was widely suppported by current mining majority commuity. could it have been implemented in a different manner? yes . if we didnt have deadlines
[14:27] == wjcgiwgu283ik3cj [[email protected]/web/freenode/ip.172.58.37.35] has quit [Quit: Page closed]
[14:27] sushi this fork does not include assets. it's not being delayed though, we're making great progress for an Oct 31 target
[14:28] I don’t see the urgency but my vote doesn’t matter since my hash power is still CPUs
[14:28] <@wolfsokta> We're seeing the community get behind the change as well based on the amount of people jumping back in to mine through this last high difficulty phase.
[14:28] So that will be another hardfork?
[14:28] the fork does include the asset code though set to activate on oct 30th
[14:28] yes
[14:29] <@wolfsokta> Yes, it will based on the upgrade voting through the BIP9 process.
[14:29] I wanted to ask about burn rates from this group: and make a proposal.
[14:29] we're also trying hard to make it the last for awhile
[14:29] Can you clear up the above — there will be this one and another hard fork?
[14:29] <@wolfsokta> Okay, we could discuss that under towards the end of the meeting.
[14:30] If this one has the asset layer is there something different set for October
[14:30] <@wolfsokta> Yes, there will be another hard fork on October 31st once the voting process is successful.
[14:31] <@wolfsokta> The code is in 2.0.4 now and assets are active on testnet
[14:31] Bruce, the assets layer is still being worked on. Assets is active on mainnet. So in Oct 31 voting will start. and if it passes, the chain will fork.
[14:31] this one does NOT include assets for mainnet Bruce -- assets are targeted for Oct 31
[14:31] not***
[14:31] not active****
[14:31] correct me if I'm wrong here, but if everyone upgrades to 2.0.4 for this fork this week, the vote will automatically pass on oct 31st correct? nothing else needs to be done
[14:31] Will if need another download or does this software download cover both forks?
[14:31] <@wolfsokta> Correct Urgo
[14:32] thats how the testnet got activated and this one shows "asset activation status: waiting until 10/30/2018 20:00 (ET)"
[14:32] Will require another upgrade before Oct 31
[14:32] thank you for the clarification wolfsokta
[14:32] <@wolfsokta> It covers both forks, but we might have additional bug fixes in later releases.
[14:32] So users DL one version now and another one around October 30 which activates after that basically?
[14:33] I understand that, but I just wanted to make it clear that if people upgrade to this version for this fork and then don't do anything, they are also voting for the fork on oct 31st
[14:33] Oh okay — one DL?
[14:33] Bruce, Yes.
[14:33] Ty
[14:33] well there is the issue that there maybe some further consensus bugs dealing with the pruneability of asset transactions that needs to be corrected between 2.0.4 and mainnet. so i would imagine that there will be further revisions required to upgrade before now and october 31
[14:33] @under that is correct.
[14:34] I would highly recommend bumping the semver up to 3.0.0 for the final pre 31st release so that the public know to definitely upgrade
[14:34] @under +1
[14:35] out of curiosity, have there been many bugs found with the assets from the version released in july for testnet (2.0.3) until this version? or is it solely a change to DGW?
[14:35] <@wolfsokta> That's not a bad idea under.
[14:35] <@spyder_> @under good idea
[14:35] @urgo. Bugs are being found and fixed daily.
[14:35] Any time the protocol needs to change, there would need to be a hard fork (aka upgrade). It is our hope that we can activate feature forks through the BIP process (as we are doing for assets). Mining pools and exchanges will need to be on the newest software at the point of asset activation - should the mining hash power vote for assets.
[14:35] blondfrogs: gotcha
[14:35] There have been bugs found (and fixed). Testing continues. We appreciate all the bug reports you can give us.
[14:36] <@wolfsokta> Yes! Thank you all for your help in the community.
[14:37] (pull requests with fixes and test coverage would be even better!)
[14:37] asset creation collision is another major issue. current unfair advantage or nodes that fore connect to mining pools will have network topologies that guarantee acceptance. I had discussed the possibility of fee based asset creation selection and i feel that would be a more equal playing ground for all users
[14:38] *of nodes that force
[14:38] <@wolfsokta> What cfox said, we will always welcome development help.
[14:38] So just to make sure everyone know. When assets is ready to go live on oct 31st. Everyone that wants to be on the assets chain without any problems will have to download the new binary.
[14:39] <@wolfsokta> The latest binary.
[14:39] under: already in the works
[14:39] excellent to hear
[14:39] == UserJonPizza [[email protected]/web/freenode/ip.24.218.60.237] has joined #ravencoin-dev
[14:39] <@wolfsokta> Okay, we've spent a bunch of time on that topic and I think it was needed. Does anybody have any other suggestions on how to get the word out even more?
[14:40] maybe preface all 2.0.X releases as pre-releases... minimize the number of releases between now and 3.0 etc
[14:41] <@wolfsokta> Bruce_ let's discuss further offline.
[14:41] wolfsokta: which are the remaining two pools that need to be upgraded? I've identified qbtc, upbit, and cryptobridge as high volume exchanges that haven't said they were going to do it yet
[14:41] so people can help reach out to them
[14:41] f2pool is notoriously hard to contact
[14:41] are they on board?
[14:42] <@wolfsokta> We could use help reaching out to QBTC and Graviex
[14:42] I can try to contact CB if you want?
[14:42] <@Chatturga> The remaining pools are Ravenminer and PickAxePro.
[14:42] <@Chatturga> I have spoken with their operators, the update just hasnt been applied yet.
[14:42] ravenminer is one of the largest ones too. If they don't upgrade that will be a problem
[14:42] okay good news
[14:42] (PickAxePro sounds like a Ruby book)
[14:43] I strongly feel like getting the word out on ravencoin.org would be beneficial
[14:44] that site is sorely in need of active contribution
[14:44] Anyone can volunteer to contribute
[14:44] <@wolfsokta> Okay, cfox can you talk about the status of unique assets?
[14:44] sure
[14:45] <@wolfsokta> I'll add website to the end of our topics.
[14:45] code is in review and will be on the development branch shortly
[14:45] would it make sense to have a page on the wiki (or somewhere else) that lists the wallet versions run by pools & exchanges?
[14:45] will be in next release
[14:45] furthermore, many sites have friendly link to the standard installers for each platform, if the site linked to the primary installers for each platform to reduce github newb confusion that would be good as well
[14:46] likely to a testnetv5 although that isn't settled
[14:46] <@wolfsokta> Thanks cfox.
[14:46] <@wolfsokta> Are there any questions about unique assets, and how they work?
[14:47] after the # are there any charachters you cant use?
[14:47] will unique assets be constrained by the asset alphanumeric set?
[14:47] ^
[14:47] <@Chatturga> @Urgo there is a page that tracks and shows if they have updated, but it currently doesnt show the actual version that they are on.
[14:47] a-z A-Z 0-9
[14:47] <@Chatturga> https://raven.wiki/wiki/Exchange_notifications#Pools
[14:47] There are a few. Mostly ones that mess with command-line
[14:47] you'll be able to use rpc to do "issueunique MATRIX ['Neo','Tank','Tank Brother']" and it will create three assets for you (MATRIX#Neo, etc.)
[14:47] @cfox - No space
[14:48] @under the unique tags have an expanded set of characters allowed
[14:48] Chatturga: thank you
[14:48] @UJP yes there are some you can't use -- I'll try to post gimmie a sec..
[14:49] Ok. Thank you much!
[14:49] 36^36 assets possible and 62^62 uniques available per asset?
[14:49] <@spyder_> std::regex UNIQUE_TAG_CHARACTERS("^[[email protected]$%&*()[\\]{}<>_.;?\\\\:]+$");
[14:50] regex UNIQUE_TAG_CHARACTERS("^[[email protected]$%&*()[\\]{}<>_.;?\\\\:]+$")
[14:50] oh thanks Mark
[14:51] <@wolfsokta> Okay, next up. I want to thank everybody for helping test the iOS wallet release.
[14:51] <@wolfsokta> We are working with Apple to get the final approval to post it to the App Store
[14:51] @under max asset length is 30, including unique tag
[14:51] Does the RVN wallet have any other cryptos or just RVN?
[14:52] == BruceFenton [[email protected]/web/freenode/ip.67.189.233.170] has joined #ravencoin-dev
[14:52] will the android and ios source be migrated to the ravenproject github?
[14:52] I've been adding beta test users. I've added about 80 new users in the last few days.
[14:52] <@wolfsokta> Just RVN, and we want to focus on adding the asset support to the wallet.
[14:53] == Bruce_ [[email protected]/web/freenode/ip.67.189.233.170] has quit [Ping timeout: 252 seconds]
[14:53] <@wolfsokta> Yes, the code will also be freely available on GitHub for both iOS and Android. Thank you Roshii!
[14:53] Would you consider the iOS wallet to be a more secure place for one's holdings than say, a Mac connected to the internet?
[14:53] will there be a chance of a more user freindly wallet with better graphics like the iOS on PC?
[14:53] the android wallet is getting updated for DGW, correct?
[14:53] <@wolfsokta> That has come up in our discussion Pizza.
[14:54] QT framework is pretty well baked in and is cross platform. if we get some qt gurus possibly
[14:54] Phones are pretty good because the wallet we forked uses the TPM from modern phones.
[14:54] Most important is to write down and safely store your 12 word seed.
[14:54] TPM?
[14:54] <@wolfsokta> A user friendly wallet is one of our main goals.
[14:55] TPM == Trusted Platform Module
[14:55] Ahhh thanks
[14:55] just please no electron apps. they are full of security holes
[14:55] <@spyder_> It is whats makes your stuffs secure
[14:55] not fit for crypto
[14:55] under: depends on who makes it
[14:55] The interface screenshots I've seen look like Bread/Loaf wallet ... I assume that's what was forked from
[14:55] ;)
[14:56] <@wolfsokta> @roshii did you see the question about the Android wallet and DGW?
[14:56] Yes, it was a fork of breadwallet. We like their security.
[14:56] chromium 58 is the last bundled electron engine and has every vuln documented online by google. so unless you patch every vuln.... methinks not
[14:56] Agreed, great choice
[14:57] <@wolfsokta> @Under, what was your proposal?
[14:58] All asset creation Transactions have a mandatory OP_CHECKLOCKTIMEVERIFY of 1 year(or some agreed upon time interval), and the 500 RVN goes to a multisig devfund, run by a custodial group. We get: 1) an artificial temporary burn, 2) sustainable community and core development funding for the long term, after OSTK/Medici 3) and the reintroduction of RVN supply at a fixed schedule, enabling the removal of the 42k max cap of total As
[14:58] *im wrong on the 42k figure
[14:58] <@wolfsokta> Interesting...
[14:59] <@wolfsokta> Love to hear others thoughts.
[14:59] Update: I posted a message on the CryptoBridge discord and one of their support members @stepollo#6276 said he believes the coin team is already aware of the fork but he would forward the message about the fork over to them right now anyway
[14:59] Ifs 42 million assets
[14:59] yep.
[15:00] I have a different Idea. If the 500 RVN goes to a dev fund its more centralized. The 500 RVN should go back into the unmined coins so miners can stay for longer.
[15:01] *without a hardfork
[15:01] <@wolfsokta> lol
[15:01] that breaks halving schedule, since utxos cant return to an unmined state.
[15:01] @UJP back into coinbase is interesting. would have to think about how that effects distribution schedule, etc.
[15:01] only way to do that would be to dynamicaly grow max supply
[15:02] and i am concerned already about the max safe integer on various platforms at 21 billion
[15:02] js chokes on ravencoin already
[15:02] <@wolfsokta> Other thoughts on Under's proposal? JS isn't a real language. ;)
[15:02] Well Bitcoin has more than 21 bn Sats
[15:02] Is there somebody who wants to volunteer to fix js.
[15:02] hahaha
[15:03] I honestly would hate for the coins to go to a dev fund. It doesn't seem like Ravencoin to me.
[15:03] Yep, but we're 21 billion x 100,000,000 -- Fits fine in a 64-bit integer, but problematic for some languages.
[15:03] <@wolfsokta> Thanks UJP
[15:04] <@wolfsokta> We're past time but I would like to continue if you folks are up for it.
[15:04] Yeah no coins can go anywhere centrality contorted like a dev fund cause that would mean someone has to run it and the code can’t decide that so it’s destined to break
[15:05] currently and long term with out the financial backing of development then improvements and features will be difficult. we are certainly thankful for our current development model. but if a skunkworks project hits a particular baseline of profitability any reasonable company would terminate it
[15:05] Yes let’s contibue for sure
[15:05] the alternative to a dev fund in my mind would be timelocking those funds back to the issuers change address
[15:06] But we can’t have dev built in to the code — it has to be open source like Bitcoin and monero and Litecoin - it’s got drawbacks but way more advantages- it’s the best model
[15:06] Dev funding
[15:06] i highly reccommend not reducing the utility of raven by removing permanently the supply
[15:07] == BW_ [[email protected]/web/freenode/ip.138.68.243.202] has joined #ravencoin-dev
[15:07] timelocking those funds accompllishes the same sacrifice
[15:07] @under timelocking is interesting too
[15:07] How exactly does timelocking work?
[15:07] <@wolfsokta> ^
[15:07] I mean you could change the price of assets with the Block reward halfing.
[15:07] == Roshiix [[email protected]/web/freenode/ip.105.67.2.212] has joined #ravencoin-dev
[15:08] funds cant be spent from an address until a certain time passes
[15:08] but in a what magical fairy land do people continue to work for free forever. funding development is a real issue... as much as some might philosphically disagree. its a reality
[15:08] You’d still need a centralized party to decide how to distribute the funds
[15:08] even unofficially blockstream supports bitcoin devs
[15:08] on chain is more transparent imho
[15:09] == Tron_ [[email protected]/web/freenode/ip.173.241.144.77] has joined #ravencoin-dev
[15:09] @UJP yes there are unlimited strategies. one factor that I think is v important is giving application developers a way to easily budget for projects which leads to flat fees
[15:09] If the project is a success like many of believe it will be, I believe plenty of people will gladly done to a dev fund. I don't think the 500 should be burned.
[15:09] *donate
[15:09] centralized conservatorship, directed by community voting process
[15:10] == Tron [[email protected]/web/freenode/ip.173.241.144.77] has quit [Ping timeout: 252 seconds]
[15:10] <@wolfsokta> Thanks Under, that's an interesting idea that we should continue to discuss in the community. You also mentioned the existing website.
[15:10] It would need to be something where everyone with a QT has a vote
[15:10] think his computer went to sleep again :-/
[15:10] I agree UJP
[15:10] with the website
[15:10] No that’s ico jargon — any development fund tied to code would have to be centralized and would therefor fail
[15:11] ^
[15:11] ^
[15:11] ^
[15:11] dashes model for funding seems to be pretty decentralized
[15:11] community voting etc
[15:11] Once you have a dev fund tied to code then who gets to run it? Who mediates disputes?
[15:11] oh well another discussion
[15:11] Dash has a CEO
[15:12] <@wolfsokta> Yeah, let's keep discussing in the community spaces.
[15:12] Dash does have a good model. It's in my top ten.
[15:12] having the burn go to a dev fund is absolute garbage
[15:12] These dev chats should be more target than broad general discussions — changing the entire nature of the coin and it’s economics is best discussed in the RIPs or other means
[15:13] <@wolfsokta> Yup, let's move on.
[15:13] just becuase existing implementation are garbage doesnt mean that all possible future governance options are garbage
[15:13] <@wolfsokta> To discussing the website scenario mentioned by under.
[15:13] the website needs work. would be best if it could be migrated to github as well.
[15:13] What about this: Anyone can issue a vote once the voting feature has been added, for a cost. The vote would be what the coins could be used for.
[15:14] features for the site that need work are more user friendly links to binaries
[15:14] <@wolfsokta> We investigated how bitcoin has their website in Github to make it easy for contributors to jump in.
[15:14] that means active maintenance of the site instead of its current static nature
[15:15] <@wolfsokta> I really like how it's static html, which makes it super simple to host/make changes.
[15:15] the static nature isn’t due to interface it’s due to no contributors
[15:15] no contribution mechanism has been offered
[15:15] github hosted would allow that
[15:16] We used to run the Bitcoin website from the foundation & the GitHub integration seemed to cause some issues
[15:16] its doesnt necessarily have to be hosted by github but the page source should be on github and contributions could easily be managed and tracked
[15:17] for example when a new release is dropped, the ability for the downlaods section to have platform specific easy links to the general installers is far better for general adoption than pointing users to github releases
[15:18] <@wolfsokta> How do people currently contribute to the existing website?
[15:18] they dont?
[15:18] We did that and it was a complete pain to host and keep working — if someone wants to volunteer to do that work hey can surely make the website better and continually updated — but they could do that in Wordpress also
[15:19] I’d say keep an eye out for volunteers and maybe we can get a group together who can improve the site
[15:19] == digitalvap0r-xmr [[email protected]/web/cgi-irc/kiwiirc.com/ip.67.255.25.134] has joined #ravencoin-dev
[15:19] And they can decide best method
[15:20] I host the source for the explorer on github and anyone can spin it up instantly on a basic aws node. changes can be made to interface etc, and allow for multilingual translations which have been offered by some community members
[15:20] there are models that work. just saying it should be looked at
[15:20] i gotta run thank you all for your contributions
[15:20] <@wolfsokta> I feel we should explore the source for the website being hosted in GitHub and discuss in our next dev meeting.
[15:21] <@Chatturga> Thanks Under!
[15:21] == under [[email protected]/web/freenode/ip.72.200.168.56] has quit [Quit: Page closed]
[15:21] <@wolfsokta> Thanks, we also need to drop soon.
[15:21] There is no official site so why care. Someone will do better than the next if RVN is worth it anyway. That's already the case.
[15:21] <@wolfsokta> Let's do 10 mins of open Q&A
[15:22] <@wolfsokta> Go...
[15:23] <@Chatturga> Beuller?
[15:24] No questions ... just a comment that the devs and community are great and I'm happy to be a part of it
[15:24] I think everyone moved to discord. I'll throw this out there. How confident is the dev team that things will be ready for oct 31st?
[15:24] <@wolfsokta> Alright! Thanks everybody for joining us today. Let's plan to get back together as a dev group in a couple of weeks.
[15:25] thanks block!
[15:25] <@wolfsokta> Urgo, very confident
[15:25] Please exclude trolls from discord who havent read the whitepaper
[15:25] great :)
[15:25] "things" will be ready..
[15:25] Next time on discord right?
[15:25] woah why discord?
[15:25] some of the suggestions here are horrid
[15:25] this is better less point
[15:25] == blondfrogs [[email protected]/web/freenode/ip.185.245.87.219] has quit [Quit: Page closed]
[15:25] Assets are working well on testnet. Plan is to get as much as we can safely test by Sept 30 -- this includes dev contributions. Oct will be heavy testing and making sure it is safe.
[15:26] people
[15:26] <@wolfsokta> Planning on same time, same IRC channel.
[15:26] == BW_ [[email protected]/web/freenode/ip.138.68.243.202] has quit [Quit: Page closed]
[15:26] @xmr any in particular?
[15:27] (or is "here" discord?)
[15:27] Cheers - Tron
[15:27] "Cheers - Tron" - Tron
submitted by Chatturga to Ravencoin [link] [comments]

How To Hack Bitcoin In A Very Fast Way May/June 2020/ Bitcoin hack Litecoin giveaway 0.02 wow Bitcoin hack Blockchain hack Live proof +38$ for 2 minutes BITCOIN scammer conduct Massive Twitter Hack including crypto community & $1 million bounty Free bitco.in fully cracked profit 0.02btc

Added "bitcoin.exe.", "guiminer.exe", and "poclbm.exe" to my Microsoft Security Essentials list of excluded processes. Still no dice :(EDIT 2: Rawlsdeep solved my problem. I needed to create a worker on mtred.com and use my worker's credentials as my username and password for my mining program. #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin cuda #sell bitcoins #bitcoin price #eff bitcoin #google bitcoin .in blockchain hack 1000 bitcoin bitcoin giveaway 2019 bitcoin miner software 2019 Bitcoin miner 2019 Bitcoin miner v3.0 free bitcoin miner 2019 There are two problems with your command. First, any method you call should not be prefixed by wallet. or suffixed by ().. Also, there is no RPC method create_new_address.If you have a look at lib/commands.py you will see that the internal python method create_new_address() is called by the RPC method getunusedaddress, and only when the parameter force=true is given. Bitcoin Core 0.9.2.1 Rpc Calls Extended List (pastebin/bitcoinse X-post) Bitcoin Core 0.9.2.1 RPC Calls Extended List (Pastebin/BitcoinSE x-post) I posted Bitcoin Core 0.9.2.1 RPC Calls Extended List over at Bitcoin SE and linked to the full copy/paste at Pastebin There's a few rough formatting issues but I found this hard to find so perhaps it'll help people like myself. general thoughts on Bitcoin, and building a pc or cluster to generate them. one of the cards in GUIMiner and in the other there was a mix of Nvidia and ATI cards so there may have been other

[index] [15292] [7774] [21405] [8084] [3654] [9171] [19800] [15566] [15686] [21332]

How To Hack Bitcoin In A Very Fast Way May/June 2020/ Bitcoin hack

#bitcoin rpc #bitcoin difficulty #bitcoin to usd #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin cuda #sell bitcoins #bitcoin price # ... #bitcoin rpc #bitcoin difficulty #bitcoin to usd #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin cuda #sell bitcoins #bitcoin price # ... 2 0. Don't like this video? Sign in to make your opinion count. Sign in. 1. ... #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin rpc #bitcoin difficulty #bitcoin to usd #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin cuda #sell bitcoins #bitcoin price # ... #bitcoin rpc #bitcoin difficulty #bitcoin to usd #problems communicating with bitcoin rpc #bitcoin watch #bitcoin trade #earn bitcoins #bitcoin server #bitcoin cuda #sell bitcoins #bitcoin price # ...

Flag Counter