Some Taiwanese are also planning lots of projects for Coco's graduation. Like setting up a website, drawing fanarts, building monument in Minecraft (or something like that).
They even hired Kuroda Takaya for some voice acting. And are now hiring advertisement companies to create printed advertisements on billboards, bus etc.
I often get incredibly pissed off at what I last described as "moronic gullibility", as well as people spreading it and making it much worse, purposeful or accidental. Some recent/semi-recent examples, avoiding the tradition "TENTH DOCTOR/JACK HARKNESS/OMEGA/RANI/ETC. TO RETURN":
Likewise, people bitching about the show or communities surrounding the show based on heavily outdated information and other people just lapping it up.
There are other things, like the BBC's approach to spoilers, but I think that's much more rational and doesn't get me quite as irrationally pissed as gullibility.
The merge is obviously the biggest upgrade coming down the pipe in terms of impact, but I'd just like to share some of my enthusiasm for other big upgrades like Verkle trees, statelessness, and state expiry. These are massive improvements on the underlying node structure and will even have a positive impact on the gas costs for certain contracts by making it more efficient to access certain data.
I'm talking like, have-a-node-on-your-phone levels of client improvement here. No need to rely on Infura when you can just send transactions out using a light client built into your wallet.
I don't understand half of the data science and math behind it but this stuff sounds incredible.
Latest project building a zkEVM rollup: https://hackmd.io/@yezhang/S1_KMMbGt. Interestingly, this is the first look at Ethereum's possible future zkEVM upgrade. Everyone thought it was 5-10 years away, but clearly zk tech is advancing exponentially.
Of course, getting the BBC to agree to not spoil things is a much harder problem. The list of things they've spoiled over the years is absolutely insane. Especially since Moffat (with the Simm reveal) and Talalay (with Gallifrey's return) were apparently both powerless to stop the BBC from spoiling things in ads, I don't know if Chibnall will be any different.
There's a growing amount of documentation and a good number of development guides on the wiki that each cover an individual concept in foundry.
If you're looking for a "Todo list" style guide that gets you from 0 to module, I wrote this guide for beginners that does exactly that:
Finally, I strongly encourage you to join the League of Extraordinary Foundry VTT Developers discord to have access to a like minded community that can help you when you get stuck.
I feel exactly the same. Our based head moderator /u/PCJonathan has compiled a list here of all the times the BBC has stupidly spoiled major plot elements for no good reason.
The State of 1559 - Update 007
> TL;DR 📝
> Large state testing is 99% done, expect a write-up soon 🔜
> EIP-1559 has been updated to be Berlin-compatible 🇩🇪
> We’ll be proposing EIP-1559 for inclusion in the London Hard Fork during the next AllCoreDevs call 🇬🇧
> Note: this doesn’t guarantee a decison will be made on the next call, or that it will be accepted!
> Miners are pushing back against EIP-1559 and others are pushing back against the pushback: lots of new write ups from both sides, and a community call is planned for this Friday ⛏
> A few bonus posts that were too good to ignore are linked at the end of this update 👇🏻
Client dev here.
All clients will have slashing protection at launch, meaning they will track your block proposals and attestations and make sure you don't contradict yourself.
Also clients are implementing a common import/export format to share that information to ease migrating across clients https://hackmd.io/@sproul/Bk0Y0qdGD
Now even with slashing protection slashing can occur if:
Also just to be clear, slashing is the result of an active malicious behavior (producing bad attestations or producing bad blocks), if you are merely inactive and miss some expected attestations/proposals you have a penalty inversely related to the whole network inactivity (very high if close to 66% validators active, and low if close to 99%).
After delving into u/lawfultots post, I found a post by Tim Beiko that goes into depth on the architecture of the clients as the merge will occur.
It seems that all hands are on deck for the Merge, with single-minded focus on getting it done. I'm damned excited by what I see.
Hey folks, happy Sunday. I spent the week going through the feedback I received on my previous v0.01 document on the EthFinance DAO idea. Changelog is on top if you want to skim for the new changes.
Once we get everything mostly nailed down, I'll make a new top-level post and start building!
I FUCKING finally have the answer as to why my validators were missing some attestations every day.
It has nothing to do with my setup. My setup has been running flawlessly since genesis.
I have missed a block pre 1024 and a few attestations until today due to client issues. (The block issue was a Prysm only issue, the attestations are all clients).
@potuz on /r/ethstaker discord just informed me that there is an issue with slots that are divisible by 32.
>Validators that are assigned the first slot of an epoch to attest are 20% likely to vote incorrectly on it. On each epoch a validator has 1/32 chances of attesting on this epoch, and a bad vote penalizes the validator for both head and target in this case. This accounts for at least (assuming perfect inclusion distance and a good vote on source) 0.65% of the validator rewards.
More info here.
Tagging /u/superphiz as he also tried to help me with this issue but we just let it go due to number of missed attestations being <1%/day.
interesting take aways:
* 1559 means no zero gas cost mev transactions anymore. base fee must be paid.
* pricing is likely going to change to account for transactions that don't care about execution order, but just want frontrunning protection.
Pretty fascinating watching the progress on the merge happening between the various execution layer and consensus layer client teams
Does anyone know why there's no update from Erigon?
I would highly recommend catching up with these two weekly informational resources:
Both are phenomenal in their own right. Go as far back as you want/need.
To answer your specific question, the final multi-client testnet is launching Aug. 4. Launch is estimated for Oct or Nov if all goes well. Otherwise likely Q1 2021 if unforeseen issues/bugs are found.
Imo, this pump is a mixture of so many factors. It’s not just related to eth2 news. It’s TA related. It’s ratio related. It’s fundamentals related. Adoption news related. If you’ve been out of the loop, sit down and invest some time in catching up. It’s worth getting the fuller picture.
Some of the many bits of news that recently came out include:
Much of this news happened this week, but other ones are a bit older. Either way, this run was long overdue.
The important thing is, as Danny reported on this week’s devs’ call, that the audit is going well, results are expected next week, and then we can “pull the trigger on everything". https://hackmd.io/@benjaminion/eth2_news/https%3A%2F%2Fhackmd.io%2F%40benjaminion%2Fwnie2_201031
Not sure if this has been posted here before, but from today's dev call:
>Progress on Blst audit? Expect final feedback next week, and can then “pull the trigger on everything”.
There's already many 2D improvements, see the preliminary changelog I wrote. Most notably, 2D soft shadows, GPU-based particles (in 2D and 3D), basic SVG importing, an high-level multiplayer API and, of course, GDScript improvements.
If you still using OPO2 listen to me carefully. Root the phone, flash Linage 15 (OREO) and you will be delighted.
Just last week I wrote a step-by-step guide for my friend who never rooted android and it went without a problem for him, so there is no reason you should be 3 major android versions behind on the phone that is perfectly capable of running latest system.
I was meaning to post it once I get more testing, but so far everything works - Fingerprint scanner, WiFi, BT, GPS, Camera, HW buttons. Only issue I run into is that you can't type to live search in the settings (but you can access everything). My phone now has 30% more battery life since Oreo has dozing + you can pull even more with greenify + on the top of that with magisk you can further make the phone feel like new flagship. Add Google Assistant, Pixel Launcher and it is almost like you have a new nexus.
Also, I covered how to do full backup, linked to video and other guides and used most up to date stuff. If you run into problems, you can message me. You can also do that if there is something unclear in that guide 🙂Or you know, enjoy probably the last patch this phone gets.
Eth2 devs call notes (not mine): https://hackmd.io/@benjaminion/B1wRBDWdd
Not really anything juicy aside from the Altair upgrade might be creeping into August now. I don't think that's a big concern as work on London and The Merge is separate. Same client teams though, so they wouldnt want it to delay for much further as Merge will be being tested.
Reposting my comment earlier about the ETHFinance DAO update as I posted it right before the daily closed yesterday. There's a changelog at the top for the sections I clarified and changed.
Appreciate your feedback, everyone!
>Eth offloading transaction processing to a separate provider means they can be hacked or screw up and all you’ve done now is securely post bad data back to L1.
This is not possible on zk rollups. Validity proofs mathematically guarantee transactions are valid and not fraudulent. zk rollups inherit Ethereum's security.
>But this won’t be any different, it won’t dramatically increase ETH users, the same people who use it now will continue, and those that don’t won’t start because there’s nothing here..
It's fine if you don't think it's going to work, but I can tell you're severely underinformed when it comes to rollups.
This should get you up to speed: https://polynya.medium.com/why-rollups-data-shards-are-the-only-sustainable-solution-for-high-scalability-c9aabd6fbb48
After you read and understood this, please come back with specific points as to why you think this is a bad approach. Me arguing with you not understanding the tech makes no sense.
That is a lot of green.
Edit: turns out you can't strikethrough a tm. Bearish /s
I am not affiliated with Flexpool, but given the influx of new miners posting here recently, I wanted to share a relevant concern about the future of GPU mining profitability. Like it says in the cross-post, check if your pool will oppose EIP 1559 and consider alternatives. Read about EIP 1559 here, here and here.
"We’re almost there! A v1.0 release candidate beacon chain spec is in the works. I believe the deposit contract deployment to be days, not weeks, away. And beacon chain genesis weeks, not months, after that."
That's what's up.
Someone in r/netsec posted their analysis here: https://hackmd.io/KwUwzAbAxgHAjAFgLRzCYSEBMCGIk5YBGyYOEhA7AGbAJRxxA===?both#
Looks like pretty old stuff for the most part.
As a side note, I haven't been to slashdot in ages and didn't realize their comment section has gotten to be a dumpster fire of that magnitude. Jesus...
Good idea! Unfortunately, I haven't been following Loopring and GME, and haven't kept up to date with Loopring's architectures unlike StarkEx/StarkNet or zkSync. This was a great summary by CryptoCanti on Twitter: https://hackmd.io/@canti/rkUT0BD8K and is a better entry point into zkRs than anything I've written.
There's also that small matter that I'm banned from r/cc :) If you want to write something, I'd be glad to review it.
For the merge spec implementation milestones, will there be a custom testnet built for testing/fuzzing, before the actual merge event?
Or would the long loved devnets described in m5 be the final testing phase before going live?
October is not realistic. Q1 2022 is possible. Continuing to quote an early and overly optimistic date as a release date is going to cause strife when it doesn't happen by then.
Lets skip the inevitable "delay" drama and start quoting what the people doing the merge work are estimating.
I definitely agree with you. Two obligatory related links:
Things the BBC have spoilt
The BBC Had No Intention Of Not Spoiling WE&T - This was all centered around a next-time trailer reveal.
The next time trailers have revealed some key moments. I simply don't understand the logic behind making half of an episode all build up to a plot reveal and then put that plot reveal in trailers and such. This is gonna be one of those things where I'm...... cautiously optimistic. The Chibby era has shown to be better in the general approach to spoiler handling in this regard, but the biggest issues of the past few years were not Moffat's doing, but rather out of his hands and pissed off numerous cast and crew. My point here is that the BBC lost so much of my respect and any trust I had for BBC PR over the Simm incident, which is gonna take years to repair.
Although we welcome any community effort to get TRTL listed on more exchanges, the current assessment of the dev team is that we are in an too early stage. Currently our daemon and wallet software has still many glitches and kinks to fix out, and as it stands now it seems that the core dev team has decided to completely rewrite the core as announced recently in the Discord. More information on the complete rewrite of the core can be found here.
Our main concern of being listed on too many exchanges before our core software and network is stable is that we will leave a bad first impression. Take for example our listing on TradeSatoshi, where apparently their team cannot even keep a our wallet running. Although, this is clearly an issue on their side as TradeOgre seems to have no problem, it still is an indicator that our software may not be stable enough; or at least user friendly enough for wide spread adoption. When we do go big, we want to do it right from the start as we only have one change.
I hope this sheds some light on why many people in the community, including the development team, are wary against any new exchange, especially an large exchange, listing. However, as I said earlier, we welcome any community effort and TRTL is a community project. Nobody can stop anyone or a group from campaigning and raising funds for more new listings :)
It's not an ETH killer. Both Gavin (co-creator of Ethereum and Polkadot) and Vitalik (co-creator of Ethereum) even says they serve different purposes in this article.
To repost my response from below, I think that tweet may have gotten ahead of themselves unless I missed something. My main source of info has been Tim Bieko, who's been shepherding info about EIP-1559 for a while.
Based on his EIP-1559 update #5, and his EIP-1559 mainnet readiness checklist, it looks like there's still some things left to do -- mainly relating to load testing, and writing reference and consensus tests.
Though those updates are a few weeks old now -- maybe a ton has happened since then!
>Phase 0: The beacon chain
>We’re almost there! A v1.0 release candidate beacon chain spec is in the works. I believe the deposit contract deployment to be days, not weeks, away. And beacon chain genesis weeks, not months, after that.
I'm excited. I'll believe it when I see it, though.
une version navigable de l'archive fuitée par Shadow Brokers décompressée sur Github :
faite par https://twitter.com/x0rz
une analyse du dump :
par Julien Voisin
Yeah, these Ms are all different stages of progression through the merge spec. They're detailed and progress is updated here.
Many clients are now up to M4 having been only shown at 1 literally a couple of days ago. M5 is the last of the stages and comprises an All-to-All persistent devnet – All ready EL and CL teams create a long-lived devnet
As I said below, their beta starts next week and they have revamped their tokenomics this week which makes RPL more attractive to accumulate.
In my view RPL is next to join things like Uniswap, Compound and Maker as key building blocks of the Ethereum ecosystem.
> In an ideal world, we would have four or more independent clients, each with less than, say, a 30% share of the network. In those circulstances, a client could go down for a while and we would barely notice it.
>Even if we can’t achieve that ideal, reducing the network dominance of a single client will lead to a more robust network. If 50% of the validators had vanished rather than 80%, it would have been a lot easier to recover. This is because, when clients drop, it affects block production, attestation inclusion, gossip effectiveness, peering, syncing: all things that have knock-on effects on the performance of the remaining validators.
Reminder for stakers/validators: try some of the other clients out! They worked better than Prysm during Medalla and it helps with keeping the beacon chain secure and working well.
This is a tutorial made by a member of the League of Extraordinary FoundryVTT Developers.
Teaches a lot about the workflow for module making.
Visiting their discord is anyway great idea. https://discord.gg/6HmqyqNV
Running The HA Corvette Job soon as an introduction to Lancer for myself and my group. I liked the scenario that was presented, but decided a more detailed battlemap might work better since I'm running the game on FoundryVTT.
Too many reasons to type them all, but I'll say probably my "favorite" reason to hate it:
Because what Lucifer desired most is to be a good father and to raise his child with Chloe, and the writers took it from him for the worst reason possible.
That reason being Lucifer and Chloe putting the wishes of their adult, clearly in pain, traumatized child above the 49 years of wishes of their as of 6.10 yet unborn, innocent baby, because ONLY that pain and trauma of Lucifer's absence will make her grow up hating him, angry at him so much that she time travels to kill him, and then after spending 3 weeks with them in the past asks them to do it to her, therefore her request is the reason for her own trauma (one timeline scenario) /or she dooms another version of herself to a fatherless childhood (multiverse scenario,) and Chloe has to carry out that request - watch her baby girl suffer and cry for her father until she grows to hate him and herself and turns into a lost soul that needs saving and finally time travels. And that is by definition child abuse.
And that's what they turned Lucifer and Chloe into (on purpose, read this collection of quotes from the showrunners/writers.)
As for the souls, they would've realized it anyway, that's what "calling" means. And Lucifer wanted to reform the system/Hell back in s5.
EIP-1559 seems officially set for London update (July). POS could arrive before December 2021
Official ETH devs updates:
I did a decently detailed review including a lot of screenshots that can be seen here.
This started as something for internal usage at LBRY but it evolved into something I'll probably run as a blog post tomorrow (aka please don't share it).
Anyone doing a collaborative analysis?
I've started a page here:
Feel free to contribute. Alternatively, if an effort is already underway please do tell me where....
It makes you spend chems to DNA sting people which means you might risk not having enough for a fight, and there's usually 2-3 lings with the objective, who are allowed to hunt and absorb eachother in the name of advancing their objectives.
And in general, even if you think it's a lame objective, /tg/ is planning on reworking lings entirely and when/if that ever happens, Fulp will change its rules to fit the new antag with the rest of the antag's rules.
Current testnet is V0.11, but V0.12 is considered the final testnet that needs 2 to 3 months for Phase 0 launch.
Edit: Here's the latest call notes indicating V0.12 is final.
As noted with the other reply, it seems Afri's tweet inadvertently confused everyone (me as well) and to be honest I've been trying to follow this since OG Casper and I'm as confused as ever... but I'm pretty confident in my 1st paragraph statement.
Tl;dr - EF continues to be amazing at everything but communications. I'll leave it at maybe I missed it, but it would be really helpful if someone of authority could just clear the air. It seems like Afri tried with that article maybe... idk. It's like frustrating sometimes to try and peice together 7 different Reddit posts and tweets to try and get 7/8ths of an answer. (Sorry, /rant over)
"A couple of mods", while using more plugins than the game can physically handle? Get rid of 20 of those plugins. Try making a bashed patch too, making one will automatically merge and disable certain plugins, but you'll probably still have to remove some mods.
Follow that guide for setting things up (if you're not using MO you can skip the MO specific steps but you'll still need Wyre Flash and FNVEdit) and then go to the "Conflict Resolution" section at the bottom.
Ben's notes are great, also in this matter:
While Eth2/consensus client devs have largely signalled a desire to get the initial Merge completed this year, at least one Eth1/execution client team is uncomfortable committing to that. My own view at this point is that The Merge is more likely to happen in Q1/2022 than this year. Other views are available: “Ethereum is About Six Months Away from Proof-of-Stake”, says Preston Van Loon in The Defiant. I warned about the culture shock of Eth2 devs running into Eth1 governance a little while back (with accompanying video).
patience is virtue.
The CSE 6040 Syllabus has a section called "How much time and effort do you expect of me?" which discusses how to get ready for Python and linear algebra. There's a few R courses on edX by Dr. Irizarry from Harvard that go from basic to more advanced.
Comparing Algorand and AVAX is like comparing Apples and Oranges. They will have different use-cases.
Algorand will be the fastest of any other chain soon in TPS with similar finality for low-value transactions as every other PoS achieving (2-5s with the caveat of security with more confirmations but not necessary for something like a $1 or $5 cup of coffee). It's already being implemented in L1 of DEXs like IDEX.
AVAX is a good project but is not going to be able to go after the same market (trading) with comparable specs to Algorand. AVAX consensus model is slower but more secure yet their security model is main chain (x-Chain) security first and foremost and "trickle-down" inherited security to subnets second by having validators of subnets use x-Chain to perform cross-chain swaps, etc.
I think both projects have legs. I just prefer the potential use-cases and ideals of Algorand but smart money would be in both (derivatives market is bigger though and that's the market Algorand could realistically take a huge slice out of.)
Qualitatively, I'm biased by the MIT branding and past-accomplishments of the people working on Algorand as well.
Did it fall through the [cracks] or is it just a major structural change with touch-points on a lot of different elements? Doesn't strike me as something that'd be wise to just ram through.
>The next implementers’ call is scheduled for October 8th, where a “mainnet readiness checklist” will be discussed.
I just can't get behind the idea that the EIP is "nowhere in sight."
A great, intelligible-to-the-layperson write-up about what happened to Medella from Ben Edgington: https://hackmd.io/@benjaminion/eth2_news/https%3A%2F%2Fhackmd.io%2F%40benjaminion%2Fwnie2_200817
A few quick updates on Loot for those who are still interested.
More Loot was launched by Dom (the creator of Loot). This is basically just Synthesized Loot turned into an NFT. People didn't like that Synth Loot didn't feel real, since it was just a seed tied to your wallet, so now everyone can mint a new loot instead.
Crypto Raiders became the first real game to incorporate Loot bags into their existing game. You get rewards for raiding Loot dungeons, passive rewards, lots of cool stuff already. I don't know if they plan on including mLoot yet, but I hope they include it in some way soon. Looking forward to seeing how other existing metaverse games incorporate Loot, mLoot, and derivatives.
No one knows yet if mLoot will be treated any differently by developers/builders than OG Loot. OG Loot may get benefits, they may not, it may vary by game/dev.
There is discussion going on now to decide if early mLoot minters will get a small AGLD airdrop to increase their inclusion in the community and any future DAO that may or may not use AGLD as part of it's voting system. It seems most people agree a small airdrop of at least 10 AGLD is the best choice but that could change.
There is a proposal/building idea from Dom to make gas-free "expansion packs" that he may or may not already be working on that would allow people to make derivatives that get given to everyone free, no gas minting. Safe to say you can replace "Synthetic Loot" in this post with "mLoot".
Probably forgot some stuff but I'll edit it if I remember more soon.
Not really a full replacement for gsuite but I've loved the speed, simplicity and collaboration features from hackmd.io. They have an opensource version of their service called CodiMD which is also forked to Hedgedoc.org. Your choice which one you want to use but the default plugins they install has been more than enough for my use cases. On top of that the fact that it's all markdown makes it easy to move platforms, not to mention that writing it is very, very easy.
With Rayonism now wrapped up there are a range of opinions on the projected Merge launch date, ranging from October, to the end of 2021, through to early 2022, but too early to be making any firm calls.
Ethereum is planning to implement something like this, see here: https://hackmd.io/@vbuterin/state_expiry_paths
The basic idea is that owners of very old UTXO need to keep track of their coins or need to query some archiving nodes (think block explorers). Then attached to the transaction is also a Merkle proof that the UTXOs are really present in the UTXO commitment. Attaching this data also increases the fee, as your transaction gets larger. The full nodes themselves store only the most recent accessed nodes (say the ones from the last year) of the Merkle tree and can use the Merkle proofs to update the UTXO commitment.
The devil is in the detail, e.g., what is the best structure to store the UTXO set. You still need to store the hash of the parts that are omitted, so if your UTXO set gets very fragmented, you don't save so much space. Also since you want UTXO commitments, the data structure and the exact expiry pattern is part of the consensus layer, so any improvements to it requires a hard fork. For ethereum's addressed based state storage another problem is that sending to a fresh address would need a proof that it is not an existing address, but at least that is no issue for bitcoin, as UTXOs are guaranteed to be unique.
For the normal 2pm this has been a good source for me. Community provides real time transcript (in Chinese) and I set my browser (Chrome) to auto translate Chinese to English so it kind of satisfies what you're after:
The proof of stake part of Eth 2.0 already launched which is the hardest part because it covers the consensus algo. Now they are deciding what goes into the first hard fork of the beacon chain and stablize the specs for sharding and ETH1 merge by Q1 to start implementation and testnets towards the end of the year.https://hackmd.io/@benjaminion/eth2_news/https%3A%2F%2Fhackmd.io%2F%40benjaminion%2Fwnie2_210129
I'd recommend the Ethereum-magicians forums here as well as the hackmd by Tim Beiko here.
Rika of that guide here. Make a bashed patch. The majority of patches are the same things that a bashed patch will do. Combining fixes with changes, as opposed to, say, extending the features of something to cover mod-added items. I link to a good guide that covers the steps of making the patch on the first page. Just make sure you've got FNVEdit (there are links to extra bits you need to download) and Wrye Flash set up, then go to the "Conflict Resolution" section. This'll cover YUP+basically anything, though you should always then check the resulting patch.
MO2 can install anything made for NMM just fine. Compared to NMM, I think you'd want a mod manager that isn't known for completely failing to install mods at times. If you fucked up your game, it's because of the mods you picked, not the mod manager. Also I'd seriously suggest against using most of those mods with FNC, they're already having issues with running completely out of memory even with the 4GB patcher. There's no use for Drag's stuff because none of those factions will be in the game, for instance.
They are either exported for windows or if they are exported for mac: they can't be opened after macOS Big Sur update. Developers can still export for Mac and make it work by using Electron.js but it's not easy! More info: https://hackmd.io/@Mirai/Steamworks_Electronjs_eng
To squeeze out more performance out of the Raspberry Pi, you can run Celeste from tty instead of from the desktop. This uses the KMSDRM driver instead, making the game very much playable at 1080p, without screen tearing! This is running on Raspberry Pi OS "Bullseye" that was just released!
I switch between different resolutions in the menu when using windowed mode. In KMSDRM, that changes the video output resolution directly, if you want to easily switch to 720p or lower for example.
Celeste is made using FNA, an open source implementation of XNA4. To make it run on ARM, I have compiled the necessary libraries that you can extract into the game folder. Follow my guide on how to get Celeste running on your Pi 4!
Can someone make a mod that replaces the strawberry with the Raspberry Pi logo please? :D
I suggest you start with this https://community.zeroknowledge.fm/t/learning-zkps-beginner-resources/302
And join the Zero Knowledge podcast telegram group.
In terms of mathematical knowledge, you will likely need to understand a bit about pairings-friendly curves and what you can build on top: https://hackmd.io/@benjaminion/bls12-381 since many ZKP protocols are favoring pairings due to their low space usage (but they require a trusted setup).
I was like, "I'm no ape I can figure this out" and whipped out google and found this: https://hackmd.io/@tompocock/Hk2A7BD6U
And as soon as I read, "... The way we visualize polynomials" I peaced out bc I do not visualize or even understand what polynomials are 🦍
At genesis, Osmosis provides two big things:
Over time there's a number of features we have in the works to continue to improve Osmosis:
We have a list of some of our research projects here: https://hackmd.io/@osmosis/B1mmhyhFO
I absolutely understand the communication from Binance et al., as they legally can't really promise anything, and they have no control over development.
But if you follow the Merge development, you might know that non-partial withdrawals are already draft-specified (big step in the land of Eth), and might even come with the Merge itself.
I should have said partial withdrawals may not be implemented, which would be required for compounding yield. Partial withdrawals are seen as much more complex and it's not clear whether they'll be supported in the initial version of the withdrawal mechanism. Here's the working version of the validator withdrawal spec.
Tim Beiko has been doing regular updates at hackmd
Per recent tweet: "1559 already implemented, just not deployed". Looks like it's undergoing final tweaks and they're prepping for large scale testing under simulated production load.
Citation on the miners? Hadn't seen anything there. Not sure how much that matters though -- the users want it, the dapp developers want it, and the PoS validators would benefit. What really matters are the node runners -- and with people spinning up more of them for PoS beacon chain, I think most of the nodes will go with it as well.
Highly recommend both.
It's a bound without any constraints. Like T: Display + 'static, but with the right hand side (right of :) being empty. This is required because to be able to use an expression containing a generic constant as a const-generic argument, it needs to be mentioned in the signature of the item that declares that constant.
T: Display + 'static
Whether this should be something library authors have to specify or be inferred in some way has been discussed at lot in rust-lang/rust#68436, personally I think it is good the way it currently works.
See also the tracking issue for <code>const_evaluatable_unchecked</code> and the corresponding Design Document.
Lighthouse is the client from Sigma Prime, but there are plenty of clients to choose from (list is a bit outdated though). The quick notes from the latest Eth2 Implementers call will provide a more recent update about the current state of the clients (call was 4 days ago).
> Mission Mojave
Absolutely not. Broken outdated mod. Whatever guide or user suggested you this should not be taken as a reliable basis anymore.
> New Vegas Redesigned 3
Debatable. Unless you already spoiled yourself most of the game you have no basis to decide if the vanilla faces require an overhaul. The extra plugins added by the mod are not worth it.
> Wasteland Flora Overhaul
Use the fertile version but without the ESP. Dont use the dead version as it just a bunch of same looking and very out of place trees.
> Bottle That Water
Unless you plan a serious survival hardcore mdoe run this kind of mini mods are just fluff that take extra space in your load-order.
You already have Nevada Skies. Never install two weather mods at once.
> Universal Air Tank
Never even heard of it, which means its far from essential.
Basic stability mods: https://www.youtube.com/watch?v=Cypqage_Pdk
Big fat long scary guide: https://hackmd.io/s/Hka6UZxqm#
My list (requires prior modding knowledge): https://www.reddit.com/r/fnv/comments/8qhhfq/list_fallout_new_vegas_suggested_mods/
Here's some good stuff: 1 2 3
I agree with the reasoning (Obligatory Link), but I do not agree with the suggestion, at least to this extent. The BBC should publicise the show. Hell, I'd say they need to publicise the show. They should just do it better and not reveal obvious major spoilers, especially when their own cast and crew disagree with it. They used to be so much better at it than they are now, even if that wasn't that great either.
I don't follow publicity of other shows as closely as I do for Who but I can't think of a single other show that has this problem this consistently to this extent (except for Robot Wars, another BBC show, that /u/sieri00 has pointed out on the Discord).
>Subnets are a core part of its architecture (tldr: they do what eth sharding is intended to deliver)
And I doubt you've checked that, because subnets have nothing to do with execution sharding. Execution shards would have shared security, but subnets do not. The entire Avalanche network is only as secure as the least secure subnet. Take it up with Gavin Wood, I think he knows a thing or two about this stuff: https://hackmd.io/@gavwood/HJrgddTxD#More-information
>but haven't had much attention yet. They'll become an essential component as adoption continues.
Good luck telling people they'll have to sacrifice composability for 4,500 TPS max (and that's after state pruning) for every subnet. This is quite frankly a laughable plan for mass adoption, as it's not even close to scalable for global demand.
If you think that implementing other VMs like LLVM is going to help, it won't by much. And you'd still only have a network of networks with individual security each. It's flawed.
>The current situation is basically down to most of us relying on Ethereum tooling we've repurposed to talk to the c-chain that doesn't handle some of the differences in Avalanches design.
The current situation is basically down to Avalanche devs claiming breakthroughs in consensus, knowing full well that consensus is the least important bit when it comes to scalability. All they did was fork geth and raise the gas limits to siphon off activity, and throw a couple hundred million in incentives at dapp devs.
Reality checks hurt, I know. Here's another one: https://twitter.com/epolynya/status/1462871295767371781
This is the latest update: https://hackmd.io/@benjaminion/B1Ip90mdt
It seems like Optimistic sync is going to take all of the clients a couple of weeks to implement, but they are working towards that.
I find that following the interop and merge-general channels in the ETH R&D discord server is very helpful in staying up to date.
I believe this is the current withdrawal spec.
>No option for partial withdrawal is suggested due to higher complexity and lower safety of possible solutions
A few points.
*We aim to become a collective in which members can learn how to make use of the network’s assets via proposals and fund projects to enhance their understanding.
Developer engagement is an important part of the Kusama ecosystem, but it is essential we also provide as many straightforward and simple on-ramps to allow non-technical end-users to participate.
The project focuses its efforts on the development of a communications strategy, brand development, educational resources for new members wishing to understand Kusama and its benefits further, and funds for the pot.*
How is this any different from any other blockchain/dapp with a Treasury and team fund?
I'll tell you how. Transparency in the allocation of funds by on-chain governance as opposed to the opaque ways other teams handle money.
This is on Kusama, the ground for experimentation. The society, as I understand it, is a social experiment. Who knows, maybe more useful societies will come out of this in the future.
In general, let's not confuse decentralization with egalitarianism. Every blockchain/dapp you support, there's a team making money behind it.
Nope, latest news from devs are quite bright, they would like to merge before December 2021 https://hackmd.io/@timbeiko/acd/https%3A%2F%2Fhackmd.io%2F%40timbeiko%2Facd-update-003
In addition to this. For the people interested in Ethereum 2.0, there is going to be AllCoreDevs call 5th of March. One of the things that will be discussed is adding the EIP-1559 to the London fork. Source: https://hackmd.io/@timbeiko/1559-updates/https%3A%2F%2Fhackmd.io%2F%40timbeiko%2F1559-update-007
we will never see "reasonable" gas prices on L1 again, even with ETH2.0, this is a misconception I've been guilty of as well. L2 is where you'll be looking for your cheap transactions in the future.
Edgington does a good job explaining: https://hackmd.io/@benjaminion/eth2_news/https%3A%2F%2Fhackmd.io%2F%40benjaminion%2Fwnie2_210213
It's already been posted today, but this is a pretty good summary:
They have a habit of doing this, so much that I include this in my obligatory link. In particular, I remember posting bits on their Facebook page immediately after air.
The worst part is, they occasionally do spoiler warnings in such useless ways for such inane shit. This one in particular pissed me off, where they spoiler tagged possibly the most harmless scene of all, which they had already teased in the trailer, yet still used it as the preview clip for the episode where they did the Simm fuckery. All for a video where practically zero people are gonna see the spoiler warning in the description before the video or thumbnail or whatever.
cryptozombies is definitely the best place, if you want to learn Solidity then you need to learn Solidity. Also the practice problems on chainshot.
here's a road map I made: https://hackmd.io/NS-XCiEbS2GUpI8Wu1Xdew
Thanks for the link, I will be sure to read it.
I was thinking about pools, as they will have the ability to extract more MEV, going by this article https://hackmd.io/@Izzy-/Eth2VevStaking
If this is correct, a person could earn more by staking via a pool than solo...which would disincentivize decentralization.
You're thinking of the blockchain trilemma that applies to Layer 1 blockchains. L2 rollups take advantage of layer 1's decentralization and security and offer scalability without sacrificing them.
Rollup sequencers may be centralized (but most of them have plans to decentralize that too) but by design there's always an "escape hatch" that allows you to withdraw your funds back to layer 1, so a centralized squencer has 0 incentive to censor your transactions (and they can't steal your funds either because the magic happens in a Layer 1 smart contract)
Here's a great piece that goes into more details
Lots of code bases have really good guides for setting things up on local. For example, here is Goonstation's: https://hackmd.io/@goonstation/docs/%2F%40goonstation%2Fdev
If you have a specific code base you want to run, just go to their github. It usually has a link to a guide like this.
I believe this has been pushed back, correct me if I'm wrong... 2nd paragraph of last section and this
>When asked about whether they would like to have a “feature fork” in December (e.g. anything outside of the difficulty bomb pushback and, possibly, some constants adjustments for EIP-1559), all teams except one would rather not have it.
> The magic of zkRs is that you don't need to worry about state expiry infrastructure - it already exists on L1!
I'm not entirely sure this is correct. The state of a rollup is not stored on L1, and so state expiry schemes on L1 would not limit the state in a rollup. If the state of a rollup were to grow too fast, it would be harder and harder to operate it as a sequencer. See for instance this paragraph.
Tldr: matic network is gonna burn the base fee like ethereum, potentially making matic deflationary. The devs say it should take a month to implement.
Here’s extra on it what the devs shared, gives a good overview and goes in-depth
>I don't blame some people for not rushing to get the vaccine. This thing was created pretty quickly, and we have no idea the long term effects. I have a girl I work with who wants to get pregnant soon, and she is hesitant due to that.
Has your work friend not been paying attention to anything for the past 16 months? There has been an abundance of information provided to the public about fertility not being affected. Here is one resource.
There are reasons for it being developed quickly, none of which have any impact on its safety profile.
Mozilla Hubs itself is open source, and it would be worth filing an issue there for IPFS support. No idea what the backend infra is, or how difficult it would be to serve that as static content over IPFS.
It is a temporary way to define const well-formed bounds. This document explains it best. In the future it might look like where (UL.unit_mul(UR)).
And as it is so often the case, Rust's syntax is very lax to make the life of macro writers easier.
The State of 1559 - Update 003 🔥
> TL;DR 👀
> Funding secured 💰. The Ethereum Foundation has made a grant to ConsenSys and the 1559 multisig 🎉
> Forked testnets 🍴 We’re exploring whether we could fork mainnet to build a large state 1559 testnet.
> Tools, tools, tools 🛠 The Besu team has been hard at work creating a suite of tools to make interacting with the 1559 testnet easier.
> Escalator Tip Simulations 🤖 Barnabé’s team has a new notebook analyzing the impact of using EIP-2593-style fees as the tip component for 1559.
> Tons of content 📝 We have a new writeup about 1559 UX, a slew of new tangential EIPs and an analysis of a 1559 implementation on another network.
>Speaking of which - I am expecting news about the deposit contract any day now. Probably about 10 minutes after I publish this :joy:. Basically, as I understand it, we are good to go: deposit contract in the next few days; beacon chain genesis 6-8 weeks later. (This is not an official statement!)
and the anticipation builds link
>With the final integration of BLS12-381 (the elliptical curve finalization that slowed things down awhile), there is nothing stopping the roll out of the deposit contract.
Not exactly. Way past my knowledge on any technical level beyond there is still one more hurdle to go.
Third paragraph of Phase 0.
Nope, Unitystation runs on Unity and is pretty much just trying to transfer everything over. SS14 runs on a custom engine and will remake many systems. Movement isn't tile based for example. You can read up on the planned changes and other things here.