How to Use a Bitcoin Blockchain Explorer Binance Academy
How to Use a Bitcoin Blockchain Explorer Binance Academy
Bitcoin Exchange Cryptocurrency Exchange Binance
BEST Anonymous Bitcoin Wallets To Use In 2020
Binance Research veröffentlicht Studie zum Telegram Open ...
How to Buy Binance Stock - Bitcoin Market Journal
Verwenden von Bitcoin anonym 99 Bitcoins
Bitcoin Mining Allocation Binance Research
Cardano's circulating supply is more fairly distributed/less dominated by large whales than ethereum despite the 2+ year spot
Data taken directly from https://app.intotheblock.com/. This is less about ethereum (the only proxy that made sense to compare) and more about how impressive it is Cardano is *arguably* the 1st Proof of Stake smart contract coin with tokenomics more fairly distributed than cryptos that started their token distribution 2-3 years before Dano's ICO. This is also the fully diluted $ada supply it includes all coins on-chain (more accurate than reported supply data that removes the coins held in IOHK/Emurgo/CF/Binance wallets from circulation). No other smart contract coin *even comes close* to this level of equitably distributed tokenomics (mostly because they are all VC coins in some cases with single whales owning 50-80% of the circulating token supply). Also notice Bitcoin is still king and has the most equitable coin distribution at 10% (for all my PoW fanboys) signaling this market clearly still rewards coins with faiequitable tokenomics, this is bullish $ADA. I directly attribute Cardano's early tokenomics success to the lack of VC hype surrounding the Cardano ICO in 2017 (funding was driven by Asian investors located mostly in Japan). Anyway you slice the data this much is true: $ETH crushed the last line of defense for PoW fanboys with tokenomics less equitably distributed than Cardano despite the 2 year+ spot, c'est la vie :) Would love to hear some feedback from the community on this. https://twitter.com/DCdoso/status/1294028811303104516?s=20 https://preview.redd.it/9np2107e8wg51.png?width=1174&format=png&auto=webp&s=e412affe98d99af3a119f64162044cba5cded0af https://preview.redd.it/qnr4vgwktxg51.png?width=580&format=png&auto=webp&s=2f172d72323183d938af9a41a2e164bf92deeab2 oof
A NanoCharts driven update for those who want to take control of their Nano and select a rep for their voting weight. For new community members, its worth pointing towards this video to learn about the ORV consensus system that Nano uses: https://youtu.be/LZ8TZFfYDcY Ideally you are taking your coins off Binance (as number 1 rep in terms of weight and you can’t pick a rep there) or removing weight from another larger rep/or a rep controlled by a large entity. Most wallets let you pick a representative, and are even starting to provide additional functionality; surprisingly the NWC mobile apps don’t allow for representative selection right now. Finding a rep can be easy using two main sources:
Nanocharts is a useful view from top reps in terms of weight and below; if you scroll down around the 133K Nano mark you’ll potentially find some reps who only need a but more weight to become a RR. NanoCharts also can help you find a rep, using its ‘need a representative’ function near the top of the page. My Nano Ninja itself is linked from NanoCharts and gives users a great source for further digging into a reps details. Its pioneered the scoring system to help users choose reps, and has even forked the ever popular NanoVault with NinjaVault (which integrates some key functions such as the scoring system). https://arewedecentralizedyet.com also gives us a wider perspective on decentralisation against other cryptos. I think the number of nodes we have without a monetary incentive is a good stat... and the it draws on the key Nakamoto coefficient from https://repnode.org/representatives/nakamoto (how many entities could collude to form a majority on the network - this number is ideally getting bigger). Unfortunately, they don't always pull the latest stats into their main screen. Further help on Nano decentralisation could be found in the #decentralise channel on Nano Discord. https://discordapp.com/invite/JphbBas As a general rule, personally I would consider the following when picking a rep:
Active in Community
Associated with a service you admire
Been around for a long time
Provider is fairly underused - we don’t want everyone on Digital Ocean
Geographic area is under represented - different jurisdictions around the world to spread risk
Confident (as possible) that the rep is not malicious
We currently have 88 Principal Representatives (RR) that help secure the network (that have over around 133K Nano voting weight) and not all of those are online right now. It would be a good milestone to have 100 RRs, and even better to have 100 RRs that are online. Since my last update (roughly) or worth mentioning:
5 less PRs than last time. I suspect the Bitcoin run has forced many to swap Nano for Bitcoin to join the fun. We've seen similar impact on PRs in the past.
https://mynano.ninja/map provided a nice overview of Nano's spread. Hopefully we'll see PRs in South America soon, then some growth in Africa/Asia.
https://mynano.ninja/account/vano A new wallet on the scene that is building up its Ninja score but could be a worth selection. Another 80K needed for this to reach PR status, a 30K improvement over last month.
Anybody from Africa considered running a node? Be good to get on the continent. Or maybe an official node could be spun up/moved there? Did u/Soluchain set up a rep in South Africa?
What if the dev fund voted for a a non official rep with good hardware and knowledge of Nano e.g. repnode, nanocrawler? Would this help increase our Nakamoto coefficient? Long term, I imagine the aim is to have no “Official” reps (which sounds centralised as a title).
With version 19 in beta, and with recent resurgence of the markets, now could be a good time go tell people about Nano and ORV! Comments in general crypto currency groups sometimes sight us not talking about decentralisation even though we are in a good position to make our ecosystem quite decentralised.
Those below Principal Representative (PR) level to make themselves more known in the community so that we can get to 100...
V19 will give us a better opportunity to measure the voting latency for PRs as a proxy for the quality of the underlying nodes (websockets will hopefully help). This could be an important factor in future Ninja scores so that users pick powerful nodes to support the network.
Another codebase that supports hardware wallets (which would be impressive for the ecosystem) or more awareness of the NanoVault derived variants so NanoVault isn’t the only place for Ledger support.
With the large number of new readers coming to this sub we need to make information easy to access so those readers can make informed decisions. We all know there is an unusually large amount of Fear, Uncertainty and Doubt (FUD) surrounding EOS. Frankly, when clear evidence is provided it’s not that difficult to see EOS for the extremely valuable project it is. This post hopes to begin to put an end to all the misinformation by doing the following:
Giving a clear and concise answer to the most frequently asked questions in regards to EOS.
Giving a more in-depth answer for those who want to read more.
Allowing readers to make informed decisions by making credible information easy to access.
As EOS climbs the ranks we need to recognise there are going to be a lot of skeptical readers coming over and posting their questions. Sometimes they will be irrational, hostile and often just looking for a reaction. We should make it our responsibility to welcome everyone and refrain from responding emotionally to provocative posts, instead providing factual and rational answers. I will add to this post as and when I can, if you have any ideas or spot any mistakes let me know and I'll get them fixed ASAP. Im planning to add a bit on the team, centralisation and DPOS, governance and EOS VC shortly but please let me hear your suggestions!
1. How do you registeclaim your EOS tokens before June 2018?
Select Metamask, MyEtherWallet, or Ethereum Wallet
Follow the guide.
Remember that the reason you need to register your Ethereum ERC-20 address is to include your EOS tokens in order for the balance of your EOS Tokens to be included in the Snapshot if a Snapshot is created, you must register your Ethereum address with an EOS public key. The EOS snapshot will take place prior to the 1 June 2018. After this point your ERC-20 EOS tokens will be frozen. And you will be issued EOS tokens on the EOS blockchain.
So PLEASE REGISTER your Ethereum address NOW, don't forget about it, or plan on doing it some time in the near future.
There are a lot of submissions about this in /eos, so rather than making a new one please reply to this thread with any questions you may have. Don't forget to join the EOS mailing list: https://eos.io/#subscribe and join the EOS community on your platform(s) of choice: Telegram, Discord and/or Facebook. And remember, if anyone instructs you to transfer ETH to an EOS contract address that doesn't match the address found on https://eos.io you are being scammed.
2. How will the token the ERC-20 EOS tokens be transferred to the native blockchain?
There isn't one! Read the long answer then read it again, registering your Ethereum wallet is mandatory!
Within 23 hours after the end of the final period on June 1, 2018 at 22:59:59 UTC, all EOS Tokens will become fixed (ie. frozen) and will become non-transferrable on the Ethereum blockchain. In order to ensure your tokens are transferred over to the native blockchain you must register your Ethereum address with an EOS public key, if you do not you will lose all your tokens! I am not going to link any tutorials as there are many that can be found by searching Google and YouTube. block.one is helping with the development of snapshot software that can be used to capture the EOS token balance and registered EOS public key of wallets on the Ethereum blockchain. It is then down to the community to create the snapshot. This snapshot can be used when generating a genesis block for a blockchain implementing eos.io software. block.one will not be launching EOS blockchains or operating any of their nodes.
Exchange Support Some exchanges have announced that they will support the token swap. Although using this method will undoubtedly be much simpler than registering the tokens yourself it also comes with its pitfalls.
It is highly likely there are going to be multiple networks running on the eos.io software that use the snapshot. It is highly unlikely that exchanges will support them all.
It is highly likely that exchanges will not support airdrops that use the snapshot.
Exchanges that have announced support for the token swap include:
EOS.IO software is aiming to provide a decentralized operating system which can support thousands of industrial scale DApps by enabling vertical and horizontal scaling.
EOS.IO is software that introduces a blockchain architecture designed to enable vertical and horizontal scaling of decentralized applications. This is achieved through an operating system-like construct upon which applications can be built. The software provides accounts, authentication, databases, asynchronous communication and the scheduling of applications across multiple CPU cores and/or clusters. The resulting technology is a blockchain architecture that has the potential to scale to millions of transactions per second, eliminates user fees and allows for quick and easy deployment of decentralized applications.
CEO Brendan Blumer - Founder of ii5 (1group) and okay.com. He has been in the blockchain industry since 2014 and started selling virtual assets at the age of 15. Brenden can be found on the Forbes Cypto Rich List. Brendan can be found on Twitter.
CTO Dan Larimer - Dan's the visionary industry leader who built BitShares, Graphene and Steemit as well as the increasingly popular Proof of Stake Governance and Decentralised Autonomous Organization Concept. He states his mission in life is “to find free market solutions to secure life, liberty, and property for all.”. Dan can also be found on the Forbes Cypto Rich List. Dan can be found on Twitter and Medium.
Partner Ian Grigg - Financial cryptographer who's been building cryptographic ledger platforms for 2+ decades. Inventor of the Ricardian Contract and Triple-Entry Accounting.
6. Which consensus mechanism does EOS use and what are Block Producers?
Delegated Proof of Stake (DPOS) with Byzantine Fault Tolerance. Block Producers (BPs) produce the blocks of the blockchain and are elected by token holders that vote for them. BPs will earn block rewards for their service, these block rewards come in the form of EOS tokens produced by token inflation.
“EOS.IO software utilizes the only known decentralized consensus algorithm proven capable of meeting the performance requirements of applications on the blockchain, Delegated Proof of Stake (DPOS). Under this algorithm, those who hold tokens on a blockchain adopting the EOS.IO software may select block producers through a continuous approval voting system. Anyone may choose to participate in block production and will be given an opportunity to produce blocks, provided they can persuade token holders to vote for them. The EOS.IO software enables blocks to be produced exactly every 0.5 second and exactly one producer is authorized to produce a block at any given point in time. If the block is not produced at the scheduled time, then the block for that time slot is skipped. When one or more blocks are skipped, there is a 0.5 or more second gap in the blockchain. Using the EOS.IO software, blocks are produced in rounds of 126 (6 blocks each, times 21 producers). At the start of each round 21 unique block producers are chosen by preference of votes cast by token holders. The selected producers are scheduled in an order agreed upon by 15 or more producers. Byzantine Fault Tolerance is added to traditional DPOS by allowing all producers to sign all blocks so long as no producer signs two blocks with the same timestamp or the same block height. Once 15 producers have signed a block the block is deemed irreversible. Any byzantine producer would have to generate cryptographic evidence of their treason by signing two blocks with the same timestamp or blockheight. Under this model a irreversible consensus should be reachable within 1 second."
7. How does the voting process work?
The voting process will begin once the Block Producer community releases a joint statement ensuring that it is safe to import private keys and vote. Broadly speaking there will be two methods of voting:
Command Line Interface (CLI) tools
EOS Canada has created eosc, a CLI tool that supports Block Producer voting. Other Block Producer candidates such as LibertyBlock are a releasing web portal that will be ready for main net launch. There will be many more options over the coming weeks, please make sure you are always using a service from a trusted entity. Remember: Do not import your private key until you have seen a joint statement released from at least five Block Producers that you trust which states when it is safe to do so. Ignoring this warning could result in tokens lost.
8. What makes EOS a good investment?
Team - EOS is spearheaded by the visionary that brought us the hugely successful Bitshares and Steem - arguably with two projects already under his belt there is no one more accomplished in the space.
Funding - EOS is one of the best funded projects in the space. The block.one team has committed $1B to investing in funds that grow the EOS echo system. EOS VC funds are managed by venture leaders distributed around the world to insure founders in all markets have the ability to work directly with local investors. Incentives such as the EOS hackathon are also in place with $1,500,000 USD in Prizes Across 4 Events.
Community Focus - The team is aware that the a projects success depends almost entirely on its adoption. For this reason there has been a huge push to develop a strong world wide community. There is already a surplus number of block producers that have registered their interest and started to ready themselves for the launch and incentives the EOS hackathon are being used to grow the community. A index of projects using EOS can be found at https://eosindex.io/posts.
Technical Advantages - See point 9!
9. What are the unique selling points of EOS?
Potential to scale to millions of transactions per second
This depends entirely on your definition of working product. If a fully featured developer release meets your definition then yes!. Otherwise the public release will be June 2018.
EOS differs from other projects in that it aims to deliver a fully featured version of the software on launch. The Dawn 3.0 RC1 feature complete pre-release became available on April 5th. This version has all the features of the final release that is due June 2018. Further development will involve preparing the final system contract which implements all of the staking, voting, and governance mechanics. The common notion that there is no viewable code published is wrong and the initial Dawn 1.0 release has been available from September 14th 2017.
11. EOS is an ERC-20 token, how can it possibly be a competitor to other platforms?
The ERC-20 token is used only for raising funds during the token distribution; all tokens will be transferred to the native blockchain once launched.
EOS team has clearly stated their reason for choosing the Ethereum network when they described the rationale behind the ICO model. Specifically, the ICO should be a fair and auditable process, with as little trust required as possible. If you believe that an ICO should be fair, auditable, and trustless, you have no choice but to use a decentralized smart contract blockchain to run the ICO, the largest, and by-far most popular of which is Ethereum. Since EOS is intended to be a major competitor for Ethereum, some have seen this as a hypocritical choice. - Stolen from trogdor on Steam (I couldn’t word it any better myself).
12. Why do the eos.io T&C’s say the ERC-20 token has no value?
The EOS T&C’s famously state:
"The EOS Tokens do not have any rights, uses, purpose, attributes, functionalities or features, express or implied, including, without limitation, any uses, purpose, attributes, functionalities or features on the EOS Platform."
This is legal wording to avoid all the legal complications in this emerging space, block.one do not want to find themselves in a lawsuit as we are seeing with an increasing amount of other ICOs. Most notably Tezos (links below).
This all comes down to legal issues. Anyone who’s been into crypto for 5 minuets knows that government bodies such as the Securities and Exchange Commission (SEC) are now paying attention to crypto in a big way. This legal wording is to avoid all the legal complications in this emerging space, block.one do not want to find themselves in a lawsuit as we are seeing with an increasing amount of other ICOs. Many token creators that launched ICOs are now in deep water for selling unregistered securities.
A filing from the Tezos lawsuit:
"In sum, Defendants capitalized on the recent enthusiasm for blockchain technology and cryptocurrencies to raise funds through the ICO, illegally sold unqualified and unregistered securities, used a Swiss-based entity in an unsuccessful attempt to evade U.S. securities laws, and are now admittedly engaged in the conversion, selling, and possible dissipation of the proceeds that they collected from the Class through their unregistered offering."
To ensure EOS tokens are not classed as a unregistered security block.one has made it clear that they are creating the EOS software only and won’t launching a public blockchain themselves. This task is left down to the community, or more precisely, the Block Producers (BPs). The following disclaimer is seen after posts from block.one:
"block.one is a software company and is producing the EOS.IO software as free, open source software. This software may enable those who deploy it to launch a blockchain or decentralized applications with the features described above. block.one will not be launching a public blockchain based on the EOS.IO software. It will be the sole responsibility of third parties and the community and those who wish to become block producers to implement the features and/or provide the services described above as they see fit. block.one does not guarantee that anyone will implement such features or provide such services or that the EOS.IO software will be adopted and deployed in any way.”
It is expected that many blockchains using eos.io software will emerge. To ensure DAPPs are created on an ecosystem that aligns with the interests of block.one a $1bn fund will be has been created to incentivise projects to use this blockchain.
“A lot of token distributions only allow a small amount of people to participate. The EOS Token distribution structure was created to provide a sufficient period of time for people to participate if they so choose, as well as give people the opportunity to see the development of the EOS.IO Software prior to making a decision to purchase EOS Tokens.”
It is also worth noting that block.one had no knowledge how much the the token distribution would raise as it is determined by the free market and the length of the token distribution is coded into the Ethereum smart contract, which cannot be changed.
14. Where is the money going from the token distribution?
Funding for the project was raised before EOS was announced, the additional money raised from the token distribution is largely going to fund projects on EOS.
A large portion of the money raised is getting put back into the community to incentivise projects using eos.io software. block.one raised all the money they needed to develop the software before the ERC-20 tokens went on sale. There are some conspiracies that block.one are pumping the price of EOS using the funds raised. The good thing about blockchain is you can trace all the transactions, which show nothing of the sort. Not only this but the EOS team are going to have an independent audit after the funding is complete for piece of mind.
From eos.io FAQ:
“block.one intends to engage an independent third party auditor who will release an independent audit report providing further assurances that block.one has not purchased EOS Tokens during the EOS Token distribution period or traded EOS Tokens (including using proceeds from the EOS Token distribution for these purposes). This report will be made available to the public on the eos.io website.”
A more complete list of EOS projects can be found at eosindex.io.
16. Dan left his previous projects, will he leave EOS?
When EOS has been created Dan will move onto creating projects for EOS with block.one.
When a blockchain project has gained momentum and a strong community has formed the project takes on a life of its own and the communities often have ideas that differ from the creators. As we have seen with the Bitcoin and Ethereum hark forks you cant pivot a community too much in a different direction, especially if its changing the fundamentals of the blockchain. Instead of acting like a tyrant Dan has let the communities do what they want and gone a different way. Both the Bitshares and Steem were left in a great position and with Dans help turned out to be two of the most successful blockchain projects to date. Some would argue the most successful projects that are actually useable and have a real use case. What Dan does best is build the architecture and show whats possible. Anyone can then go on to do the upgrades. He is creating EOS to build his future projects upon it. He has stated he loves working at block.one with Brendan and the team and there is far too much momentum behind EOS for him to possibly leave.
No one could have better knowledge on this subject than our Block Producer candidates, I have chosen to look to EOS New York for this answer:
"DDoS'ing a block producing is not as simple as knowing their IP address and hitting "go". We have distributed systems engineers in each of our candidate groups that have worked to defend DDoS systems in their careers. Infrastructure can be built in a way to minimize the exposure of the Block Producing node itself and to prevent a DDoS attack. We haven't published our full architecture yet but let's take a look at fellow candidate EOSphere to see what we mean. As for the launch of the network, we are assuming there will be attacks on the network as we launch. It is being built into the network launch plans. I will reach out to our engineers to get a more detailed answer for you. What also must be considered is that there will be 121 total producing and non-producing nodes on the network. To DDoS all 121 which are located all around the world with different security configurations at the exact same time would be a monumental achievement."
18. If block producers can alter code how do we know they will not do so maliciously?
Block producers are voted in by stake holders.
Changes to the protocol, constitution or other updates are proposed to the community by block producers.
Changes takes 2 to 3 months due to the fact block producers must maintain 15/21 approval for a set amount of time while for changes to be processed.
To ensure bad actors can be identified and expelled the block.one backed community will not back an open-entry system built around anonymous participation.
For this question we must understand the following.
Governance and why it is used.
The process of upgrading the protocol, constitution & other updates.
Dan’s view on open-entry systems built around anonymous participation.
Governance Cryptography can only be used to prove logical consistency. It cannot be used to make subjective judgment calls, determine right or wrong, or even identify truth or falsehood (outside of consistency). We need humans to perform these tasks and therefore we need governance! Governance is the process by which people in a community:
Reach consensus on subjective matters of collective action that cannot be captured entirely by software algorithms;
Carry out the decisions they reach; and
Alter the governance rules themselves via Constitutional amendments.
Embedded into the EOS.IO software is the election of block producers. Before any change can be made to the blockchain these block producers must approve it. If the block producers refuse to make changes desired by the token holders then they can be voted out. If the block producers make changes without permission of the token holders then all other non-producing full-node validators (exchanges, etc) will reject the change.
Upgrade process The EOS.IO software defines the following process by which the protocol, as defined by the canonical source code and its constitution, can be updated:
Block producers propose a change to the constitution and obtains 15/21 approval.
Block producers maintain 15/21 approval of the new constitution for 30 consecutive days.
All users are required to indicate acceptance of the new constitution as a condition of future transactions being processed.
Block producers adopt changes to the source code to reflect the change in the constitution and propose it to the blockchain using the hash of the new constitution.
Block producers maintain 15/21 approval of the new code for 30 consecutive days.
Changes to the code take effect 7 days later, giving all non-producing full nodes 1 week to upgrade after ratification of the source code.
All nodes that do not upgrade to the new code shut down automatically.
By default, configuration of the EOS.IO software, the process of updating the blockchain to add new features takes 2 to 3 months, while updates to fix non-critical bugs that do not require changes to the constitution can take 1 to 2 months.
Open-entry systems built around anonymous participation To ensure bad actors can be identified and expelled the block.one backed community will not back an open-entry system built around anonymous participation. Dan's quote:
"The only way to maintain the integrity of a community is for the community to have control over its own composition. This means that open-entry systems built around anonymous participation will have no means expelling bad actors and will eventually succumb to profit-driven corruption. You cannot use stake as a proxy for goodness whether that stake is held in a bond or a shareholder’s vote. Goodness is subjective and it is up to each community to define what values they hold as good and to actively expel people they hold has bad. The community I want to participate in will expel the rent-seeking vote-buyers and reward those who use their elected broadcasting power for the benefit of all community members rather than special interest groups (such as vote-buyers). I have faith that such a community will be far more competitive in a market competition for mindshare than one that elects vote buyers."
19. What is the most secure way to generate EOS key pairs?
Block producer candidates EOS Cafe and EOS New York have come forward to help the community with this topic. The block producer candidate eosnewyork has kindly posted a tutorial on steemit detailing the steps that need to be taken to generate key pairs using the official code on the EOS.IO Github. The block producer candidate eoscafe has gone a step further and released an Offline EOS Key Generator application complete with GUI for Windows, Linux & Mac. Not only can this application generate key pairs but it can also validate key pairs and resolve public keys from private keys. This application has also been vouched for by EOS New York
Dev meeting? Would say so, yes The people are still exhausted from the payment ID meeting :) Guess we could ping some people vtnerd, moneromooo, hyc, gingeropolous, TheCharlatan, sarang, suraeNoether, jtgrassie Anyone up for a meeting? Yep I'm here Here o/ Perhaps we should just start and people will eventually hop in? oof sorry guys, I'm working on the new FFS and I forgot all about this. Got a couple of new volunteers. This literally might be able to launch tomorrow. I know that. It's called "flow" :) I could run if you're out of time? go for it dEBRUYNE you guys are going to like this new FFS. We're like 99% done. Hi rehrar: someone else do the milestone thing already? All right, jtgrassie, perhaps you'd to start w/ briefly describing your most recent PR? https://github.com/monero-project/monero/pull/5091 oneiric, xiphon did everything like....everything As far as I can see, it allows the user to push his transaction over I2P, thereby masking the origin IP of the sendeuser great And it hooks into vtnerd's PR right? Sure. It basically just builds on vtnerds Tor stuff. sorry dEBRUYNE Really not much added. I have it running and tested. From the perspective of the user, what needs to be configured exactly? Nice Assuming the PR is included in the release binaries I'm using knacccs i2p-zero duirng testing but will of course work with any i2p setup sorry dEBRUYNE <= Np Looks a little like dams breaking, now that we have some dark clouds over Kovri and people take matters into their own hands ... User needs to run i2p, expose a socks service and and inbound tunnel. Basically same as Tor Okay, so should be reasonable as long as we write proper documentation for it (e.g. an elaborate guide) rbrunner, yes, knaccc credit for jumping on i2p-zero really dEBRUYNE: documentation monero side is kindof done. i2p side is very much implementation specific. I suppose we could write some guides for the most popular implementations? e.g. i2p-zero aims to be zero conf, but i2pd or Kovri would be differnet. I see, great vtnerd___: Do you want to add anything? could amend the current kovri guide for monero use from --exclusive-peer to the new proxy support Now I have i2p-zero running and tested with the #5091, I plan to jump back over to helping knaccc on getting that polished. I added support for socks proxy in the basic wallets ^ excellent Yes vtnerd___ I havent tested it yet but looks sweet. So connections to `monerod` over Toi2p are possible within wallet cli and wallet rpc Awesome This also implies auth+encryption even if ssl is not in use (when using an onion or i2p address) All right moneromooo: are you here? If so, could you perhaps share what you've been working on? I am. I revived the SSL PR, more stuff on multi sender txes, an implementation of ArticMine's new block size algorithm. I presume a multi sender tx works similar to multisig insofar as the senders have to exchange data before the transaction can be performed right? Yes. There are 2 SSL PRs. What's the diff? Theoretically this would also allow the sender to provide an output right? Which would be kind of similar to Bitcoin's P2EP The second one adds some things like selecting a cert by fingerprint. Yes. (for the first sentence) All right, awesome For anyone reading, this breaks the assumption of the inputs belonging to a single sender, which makes analysis more difficult Nice side-effect. Much work coming for the various wallets to support that rbrunner: Anything you'd like to share in the meeting btw? Yes, just a little info I have started to seriously investigate what it would mean to integrate Monero into OpenBazaar I have already talked with 2 of their devs, was very interesting In maybe 2 or 3 weeks I intend to write a report Too early to tell much more :) Soon^tm I guess :) Yep Currently wrestling with Go debugging whole new world moneromooo: Has pony recently shared any insights regarding the upcoming 0.14 release btw? No. All right I would love to see the tor & i2p PR's merged sooner rather than later so we can get more testing done. ^ +1 Isn't that famous early code freeze already on the horizon? fluffypony, luigi1111 ^ I suppose I could provide a little update regarding the GUI btw As always, lots of bug fixes and improvements :-P selsta has recently added a feature to support multi accounts dsc_ has revamped the wizard and will now start working on implementing the different modes and a white theme dsc_ is working fulltime on the GUI already? yes :) dsc_ is bae In light of the recent payment ID discussion, we've also, by default, disabled the option to add a payment ID unless the user explicitely activates the option on the settings page rehrar ^ nice I spoke about this yesterday at the coffee chat, this is not a good decision. How does it handle integrated addresses? The same way? rehrar ? For the next many months, we are still stuck with PAyment IDs in the ecosystem. Making it harder for people to access them will make Monero suck so hard to use for the average person for many months. i agree with rehrar Remove the option of Payment IDs when we remove Payment IDs rehrar: The new GUI release won't be live until probably mid march though Which is a few weeks in advance of the scheduled protocol upgrade Payment ID removal comes in October right, but Payment IDs are not removed in March Did we not have loose consensus on removing the old, unencrypted payment IDs in march? they are removed in October We had discussed a deprecation in March and a ban in October ok, then if we are going to do that, we have to commit to it and contact the exchanges like Binance that use them and get rid of them in the next few months (of unencrypted) Binance is huge, and if they still use them, then people will be very upset that they can't deposit or use Payment IDs easily I'm just speaking from a UX perspective. I thought it was unencrypted in April and possibly encrypted in October Yes I do agree Timeline and notes: https://github.com/monero-project/meta/issues/299 impossible to remove them for march, many exchanges still use them We can defer it to the 0.15 release if needed Well, that wasn't the impression for them log that I just read today This was all discussed in the earlier meeting linked above We have to force the ecosystem off of Payment IDs before we remove them from the UI, is all I'm saying Remove != make difficult to use ... or make them more difficult there, right? ping sgp_ sarang, I understand, and I agreed with you during that meeting. But then I started thinking of it as a UX person, which I am. And that huge massive problem leapt out at me i think making them difficult to generate is a good idea but making them difficult to consume and use is a bad idea well, maybe not a good idea, but a better idea ^ If we defer the decision to depriciate long payment IDs to october, won't we have the same issue then? The UI can gave an expandable payment ID field like MyMonero and we can still call it deprecated It is foolhardy to remove an option that the ecosystem uses. So I suggest we keep the Payment ID in the UI until October when they are completely banned. no dEBRYUNE, because they will be banned via consensus sgp_ imo it may be a misdirection of dev resources to add that since things are proceeding in the short term rather than long term but this is a relatively minor point Nothing matters til exchanges change All right The issue is that consensus will still have them in April, and exchanges won't upgrade because they are still allowed. Thus they must still be in the UI. endogenic these changes are already merged in the GUI to hide it like you do ok But when they are banned, exchanges are forced to upgrade or stop using Monero, so we can remove them safely because they won't be in use rehrar: that's a strong assumption sarang that they will upgrade? yes if they don't, then they can't use Monero If exchanges require pid, users need a way to set a pid. Making it hard for the user in the interim is just going to be a nightmare. we have decided to take our "stand" in October A way that is not too hard, then To be clear, we still intend to deprecate long encrypted payment IDs in April right? But no enforcement until October the term "deprecated" doesn't mean much if it's still allowed, and used in popular places yes, as far as I understand it jtgrassie, exactly True I suppose dEBRUYNE: we need to be more specific when talking about deprecation the person who suffers is the user There are two proposals for GUI deprecation: 1. Hide it in the send screen with a simple option to expand (currently merged iirc) 2. Hide it completely in the send screen unless users enable the field in advanced settings (PR'd but not merged yet iirc) What are the arguments for 2? Both are poor options, but 1 is better than 2 by a long shot Well the people who need to be made to "suffer" are the exchanges. And I don't see a way to make exchanges "suffer" other than by having their suffering customers complain to them constantly that they need to update. ^ CLI has something similar where users need to set a manual payment ID transfer mode. Not sure if it's merged yet the way to make the exchanges suffer is when we ban PIDs. They either upgrade or don't use Monero. exact;y Agree with rerahr here have exchanges been provided with clear, practical, sufficient technical upgrade plans for supporting what they're doing with PIDs but with subaddrs? Both are poor options, but 1 is better than 2 by a long shot <= I wouldn't call 1. a poor option. Have you actually checked how it looks? Because it states "Payment ID" and a user has to click on the + to expand the field endogenic: yes the email when out. Blog post coming soon, but contains the same info as the email also the exhcnages' users are often using wallets that don't support subaddresses ok great as well, it should be noted that the timeline for exchanges to upgrade is September, not October when the fork is. Which wallets are that? Rehrar: I don't see option 1. causing any issues/confusion i guess it doesnt matter too much if withdrawing as a personal user the main address should suffice Because September is when the new versions will be coming out without PIDs in the UI If there's opposition to 2, 1 is fine. We can still call it deprecated which is the optics we need anyway exchange users are often just using other exchanges lol. No wallets involved. dsc_ dEBRUYNE, ok, I trust you guys here then rbrunner: i was thinking mymonero last i heard Ok pigeons: rbrunner yes receiving on subaddresses won't be supported yet sending to them has been possible though and yes as learnandlurkin says often they withdraw to other systems like exhcnages that also dont yet support subaddresses I really can't come up with any good argument for 2. right now endogenic: seems not much of an issue then. Exchanges will typically support withdrawals to both subaddresses and plain addresses (especially if we are going to force them to use subaddresses) For deposits, MyMonero works properly if the user sends to a subaddress Actually the second solution was already merged: https://github.com/monero-project/monero-gui/pull/1866 Maybe not enough eyes watching :) The important thing is to have done something to justify having a big "DEPRECATED IN APRIL" stamp on PIDs to spook exchanges in the interim This was for solution 1: https://github.com/monero-project/monero-gui/pull/1855 The Monero Community Workgroup will start making noise everywhere we can to exchanges, and everywhere else that will listen. Try to get on those garbage news sites also. So everyone knows that deprecated in April, and banned in September Hey, for solution 1, write "Payment ID (optional, deprecated)" or similar there rbrunner: noted rehrar: probably wait until the blog post, but it should only be a few days Maybe a Reddit sticky post would be useful? With the blog post If people are over freaking out about the hashrate or terabyte blockchain :) sigh Any questions for the MRL side? Is someone checking ArticMine's block size changes for weird behaviour in some cases etc ? How would such testing work? Private blockchain?