EOS Amsterdam - EOS Telegram - EOS BlockPros Summary - Sep 19-20th

in #eos6 years ago

photo524773754814965686.jpg

Edgar | EOS Costa Rica
We launched the EOSurf sign up! Be sure to visit EOSurf.com to sign up for updates and help customize these EOS offsites by filling out our surf-vey!

https://docs.google.com/forms/d/e/1FAIpQLScuRPtAVLBetkdAQKuHi72e0l1W7df5l70XW88bRBDwhPRclQ/viewform?usp=send_form

Philip - EOS Detroit (eosdetroit.io)
Hey everyone, just thought I would share the livestream link for today’s EOS Alliance call. Starting shortly!

fonsolo - EOSTalk.io
Hey guys, I am working on amassing a community of business-minded intellectuals to share valuable knowledge and, in return, receive rewards from the community. The community is known as Morte et Tributa (MET) and it is on the Whaleshares.io platform. If any of you are interested you can check out our introductory post via https://whaleshares.io/business/@met/met-morte-et-tributa.

I am hoping that through this community we can fight for fair crypto-regulation, because the regulation that we currently are subjected to is pretty ridiculous.

iamblissss
Does anyone have a website link that shows how many EOS accounts have been created?
Matt Witherspoon
https://eosflare.io

Crypto Feez
https://www.youtube.com/c/CryptoFeez/live

Bart Wyatt
for the most part there have been no changes between 1.0 and 1.3 that affect the actual block chain (save one, in my memory). There have been a few subjective measures added which are not part of consensus but helped to work around issues that users were experiencing during. All this is to say that, a version like 1.3 is more an upgrade to the software used to maintain the blockchain, not an upgrade to the blockchain itself. There is no need for producers to force anything. If they like the software improvements they can deploy it

Cesar Nebula Protocol
we have tools to detect that kind of behaviours and voters could decide to stop supporting them to get into top21 a BP that performs better 🙂
https://labs.eostitan.com/#/block-producer-performance/?chain=kylin&account_action=eosmechanics-cpu&aggregate=mean&min_events=1&time_period_string=24-hours&interval_minutes=60&scale=20000

this is one tool where you can see the performance (and the implementation of 1.3 improvement), that is a testnet for now

David Floyd
Hi all, I apologize if this isn't the best channel to post this question, but is anyone aware of a detailed post-mortem on the blockchain halt that occurred on June 16? This post said one would be coming, but I'm not finding it https://steemit.com/eos/@eosargentina/statement-regarding-eos-mainnet-status

Thomas Cox
The PR with some details is here:
https://github.com/EOSIO/eos/pull/4158

My best understanding follows.

The system needed to check deferred transactions differently than it was. A non-deferred Tx, you can check it to see if it's failed or not, and handle each of those two cases appropriately. A deferred Tx is in neither state, until later when you execute it. The code wasn't checking the deferred Tx at EXECUTION time (which is later, remember) in the correct way, which led to a "weird state" (technical term) that confused the system and prevented futher blocks from being created.

This led to a PAUSE because of a test elsewhere in the code, that said if LIB (Last Irreversible Block) was more than (I think it was) 20 minutes ago, you should stop making more blocks and wait.

@eosnewyork may remember more.

We (collectively) did promise a more detailed write-up and that never happened, so that's a bit of a dropped ball.
I remember this happened on a Saturday, right before a family birthday party. Pretty brisk response by the BP community, too.
First notice in this channel is here, you can revisit the fun:
https://t.me/EOSPros/37676

A few folks heard "the chain has paused" and mentally translated it to "Some person has the power to unilaterally pause the chain! Centralization!" which wasn't the case. More accurate to say the chain "paused itself" per the code for not adding blocks when LIB isn't advancing.

Kevin Rose - EOS New York
We are requesting feedback from the community: https://medium.com/eos-new-york/free-market-dispute-resolution-regarbitrator-regforum-request-for-comments-74e31bcb84b0

Hezi Hershkovitz
for anyone struggling like I was with the the Not producing block because I don't have the private key for EOS7EarnUhcyYqmdnPon8rm7mBC... error, I made a steemit post about my mistakes when creating a node and connecting it to mainnet
https://steemit.com/eos/@hhezi/tips-for-connecting-eos-node-to-mainnet
I hope it helps

Kyle - EOSVIBES
I’m not keen on some arbitration forum making orders willy nilly about protocol level changes.
Without them being specifically dapp related

Josh Kauffman - EOS Canada 🇨🇦
but you're bringing something else into the proposal. NY is proposing a way for arbitrators and arbitration forums to register in a way that we can all verify on chain. Is that a good idea, or not. That's the question that matters here. Not really fruitful to bring up a separate concern about base layer vs app layer.

Kyle - EOSVIBES
It’s a great approach by EOSNY and I fully support it on the dapp layer.

I think it’s helpful to extrapolate and explore the idea as to it use case because this is going to be a major focal point when it comes to the community making decisions about ECAF and where that sits in all of this.

Kevin Rose - EOS New York
Use case: You are building Hirevibes and you contract me as a front-end developer. We execute an escrow contract on-chain with an associated Ricardian that outlines the deliverables of the project. Funds are submitted to the escrow contract. I deliver the front-end code and sign it over and you aren't happy with what I deliver. But I send over the command to the smart contract to release the funds anyway. You call the contract into a dispute mode and the owner permission of the contract is delegated to the arbitration forum that we outlined in our original contract. We arbitrate the dispute, the arbitrator issues an award and possibly sends it to block producers, the block producers move the funds to the target account outlined in the award. The reason the BPs are able to follow the arbitral award is because the forum and the arbitrator have both registered themselves on chain using the commands we outlined in our proposal.

Kyle - EOSVIBES
For the record; we incubated the HireVibes dapp and now it’s a stand alone business almost ready to launch

Kevin Rose - EOS New York
Have ECAF, don't have ECAF. Have an arbitration clause in the constitution, or don't. The community can decide. We want to build dispute resolution between explicitly consenting parties.
Contract enforcement, transactional confidence, dispute resolution. These will be the buzzwords of next year in blockchain.

Yves La Rose - EOS Nation
EOS Nation is also fully on board with what is being proposed, and has been very vocal about this since you presented the idea publically for the first time a while back.

I am also mearly wondering if this is indeed accurate, or if perhaps it is too simplistic "A full arbitration clause in the constitution doesn't seem to be helpful outside of theft or lost keys."

Will M! @UnificationFoundation
Is 4 % expected to stay the total inflation? How much is planned to be kept for Dapp development at this time?

Kevin Rose - EOS New York
Nothing can be decided until referendum is available.

Sort:  

@eosamsterdam, I gave you a vote!
If you follow me, I will also follow you in return!

Congratulations @eosamsterdam! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :

Award for the number of posts published

Click on the badge to view your Board of Honor.
If you no longer want to receive notifications, reply to this comment with the word STOP

Support SteemitBoard's project! Vote for its witness and get one more award!