The 13th of September
Alexandre Bourget - EOS Canada addressed a question posted earlier by Dafeng Guo | @eosasia | myeoskit.com
“@wanderingbort when will more verbose logging be available? That will provide more visibility into the tx dropping issues.”: btw you can try to use push_transaction here: https://kylin-push-guarantee.eoscanada.com .. it's in beta, but does provide a stronger guarantee than the normal push_transaction: it ensures the transaction is in a block before returning and adds block_id and block_num to the output.. so you can confirm with a get_block instead of a get_transaction (which requires the history_api, etc..)
All other endpoints forward to standard nodeos RPC.. so it's a drop-in replacement. Please test it.. we'll ship that on mainnet once we're more confident.
Also, we have an alpha version of the same thing but awaiting irreversibility (it'll wait on that HTTP connections until it passes the LIB barrier). Tell me if you're interested..
Alexandre Bourget - EOS Canada suggested testing his beta version for web sockets: PM me.. I want to understand your use case because we're building dedicated processing pipelines .. some want table deltas, some simply want transactions that include given actions, some want RAM consumption deltas..
Ariel - EOSeoul.io presented his gambling dApp: “NEOWIZ PLAY STUDIO, is a game developer and service operator and is currently no. 1 in mobile social casino category in Korea. It has much interest in blockchain technology. We have been established to commercialize the technology based on that interest.
We believe that the blockchain technology can be a stepping stone to open up new possibilities on existing business models. With that in mind, we focus not only on technical research but also on the actual business application. In close collaboration with the EOSeoul team, an EOS Block Producer, and also a NEOWIZ Group affiliates, we are constantly monitoring trends related to blockchains and exchanging a lot of ideas.
https://medium.com/nblab/a-rng-enabled-dapp-demo-release-by-nblab-11fefe85a6da”
and it got negative reaction from users:
Nathan | GenerEOS | eostoolkit.io
this does provide an interesting case study to how quickly the community identifies apps that make suspicious tx requests
it also highlights how easy a bad actor can do this if they ask for private key directly
Douglas Horn | Telos
I looked at the site... how are people still putting private keys into accounts? Such an easy social/psychological exploit here to rob people if done by had actors. (I'm not accusing, but every time a dapp does this, it makes the public more accepting of practices that end with theft.
Syed | bloks.io | EOS Cafe Calgary 🇨🇦
One thing I am not sure about is fork handling in the mongo plugin, anyone know how that works?
Igor Lins e Silva - EOS Rio
have no idea, that can be a problem for multiple nodes inserting
this was the reason i was pushing to elastic only after irreversible
宋 遁一@GEOS
https://steemit.com/eos/@geos.one/the-opponent-voice-to-ubi-uri-from-chinese-eos-community
Stéphane Duchesneau - EOS Canada
container_memory_rss" value from our monitoring to exclude caching/buffers)
We have 4 web-facing nodes running 1.2.5 and 4 nodes running 1.1.6.
The 1.1.6 nodes (top 4 in graph) have been restarted 26h ago and are using between 6-7GiB RAM
The 1.2.5 nodes (bottom 4 in graph) have restarted 18h ago and are using between 4.7-5.1GiB RAM
No clear "memory leak" pattern in neither of those. Do you guys see similar behaviour ?
CPU usage is low on both node versions, ~25%. Should we ungreylist blocktwitters and kindly ask them to start spreading their love again ? ^_^
Kedar Iyer - Everipedia - LibertyBlock
reminder to everyone to review and sign the proposal here:
cleos multisig review argentinaeos chngzhaoauth
https://eosauthority.com/approval/view?scope=argentinaeos&name=chngzhaoauth
Zhao Yu@ EOSLaoMao.com
this proposal is a demonstration to change an account’s key without sudo contract, initiated by EOSArgentina using Mallman: https://github.com/EOSArgentina/Mallmann/tree/master/code
it’s been tested on Kylin testnet, worked as expected.
jem commented regarding proposal purpose:
Anticipating any possible arbitration order to change an account's keys, possibly to restore a stolen or lost-key account.
Kevin Rose - EOS New York
And also, help fix a broken contract on a chain with the consent of the owner. All without SUDO
Hubert Chang EOSeoul.io/NBLab.io
https://medium.com/nblab/update-news-on-three-stars-slot-7ac464bd01ff
Kevin Rose - EOS New York
Here's a write up that was done:
As a dApp platform it is important that EOS is equipped with the tools to improve the quality of life its developers. A core design feature of EOS is the ability to update smart contracts that have been deployed and to do so without a hardfork. But, there may come a time where a smart contract is not behaving as expected and cannot be updated by its owner. During this time, it should be a core competency of BPs to quickly and efficiently halt the smart contract that is behaving unexpectedly and deploy new code that is provided by the original contract owners. To this end, we are seeking to test custom crafted msig functions that would allow BPs to regain control of such a rogue contract and fix it. What we are proposing is that we will perform a live test on a mainnet account that has been created by and is currently operated by EOS Lao Mao. They have proven that they are the creator of the account and have given their consent for BPs to change the owner key of the account. Pursuant to the constitution, Article III Rights, "The Members grant the right of contract and of private property to each other, therefore no property shall change hands except with the consent of the owner, by a valid Arbitrator’s order, or via community referendum. This Constitution creates no positive rights for or between any Members." We have received consent of the account owner, we are thusly authorized to act on their behalf and alter the keys per their request. This notice is to inform you of such a test and to ask that, should you agree with the purpose of the test, you approve of the msig transaction which is proposed.
Zhao Yu@ EOSLaoMao.com
it’s a demo, so I created the updatemyauth account, and I grant my consent for TOP 21 BPs to change the key of it, here is the twitter: https://bloks.io/transaction/1334c2f83abfcb680fd04ca52c99b7943428389678ebf6b27be447bbe9497dd4
Eric - sw/eden
The way I see it...
The owner of the account to be changed has given his permission for us to change it. Even requested it. This is in accordance with how EOS is supposed to work.
The argument against is that of censorship. I agree with Marshall on that general point. However... This case seems to me to be quite clear.
The proposal looks good from a technical standpoint.
I will be approving it unless convinced otherwise.
Still 25 hours left. So I will read through any and all arguments that come to me the coming 8 hours, and if not convinced otherwise approve when I wake up in the morning.
Matias Romeo (ElMato)
If eosio.sudo isn't implemented, we should NOT be able to perform sudo actions.
Impossible, or you need to re-write EOSio
Guillaume - EOS Titan
my understanding of the proposal and associated code is that they transform the eosio.prods into some sort of super account that can do just about anything, then they change the keys to the account, then revert back eosio.prods to the default state. I don't see any way to prevent it really
Yves La Rose - EOS Nation
In Seoul, the general consensus was that it should be.
So it begs the question, why aren't we (putting that up for a vote, if that's really what we're doing here).
Kevin Rose - EOS New York
I think the point of Argentina's work was that there shouldn't be such a big deal made over SUDO because
- If there are bad actors they will just do it anyway
- It's in the white paper that BPs can do this
- It can be done without SUDO so who cares if it's implemented or not?
Nate D - Aloha EOS
Makes sense. I was more trying to get a read on if there was a preference of Mallmann over sudo from the BP community for any reason. For example I've seen mentions of sudo complexity.
However it sounds like it was more just a PR issue and sudo is preferred.
Sharif Bouktila - eosDublin
Jeez guys we’ve got ourselves in a right muddle here.
What is the value in proving 15/21 have power to do something.
Who are we proving this to?
The constant fear of PR backlash or community concern is way over cooked.
The reality is the majority by volume and stake either don’t care or just want us to do our jobs.
Being able to convince 15/21 BPs to do something non-essential / non-value add on Mainnet is bad for the whole centralization debate.
I really appreciate your work. It took me a long time to get the followers I have. Luckily their are tools like steemvoter, vote4vote. steemengine etc. to help out minnows like me.
Congratulations @eosamsterdam! You have completed the following achievement on the Steem blockchain and have been rewarded with new badge(s) :
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