https://t.co/FTVIwYWKMh
Thanks to the growing number of people who @getMaiar & engage with the @ElrondNetwork ecosystem, the number of accounts doubled to over 320k & we’re over 2.5M TXs, an unprecedented adoption level for a 6 months-young mainnet.
#hypergrowth100 Day 40
Weekly #elrondtech ⬇️
https://t.co/FTVIwYWKMh
https://t.co/29I6YRtjud
https://t.co/wh6BIBeDUd
- Integrated new Arwen and new features of Arwen into elrond-go. Added a set of integration tests for different scenarios.
- Fixed a bug in Arwen VM which did not let one contract to deploy multiple contracts.
- Testing the new Arwen async-calls & promises
- Arwen & elrond-wasm testing of various scenarios involving async calls and ESDT token transfers.
- Continuous integration improvements - run tests on pull request (arwen-wasm-vm - added; elrond-wasm-rs - in progress)
Learn more about our VM: https://t.co/U6R1xN4gb5
- Worked on the NFT standard for elrond-go. Sharded NFTs where users will keep their one NFTs at their own address. A lot of features here: like creating a brand, creating a marketplace without smart contract (will accept any value - ESDT / eGLD).
- Updated all other major 3-rd party libraries to their latest versions
- Fixed several tests that had nondeterministic execution paths leading to different code coverage values.
- Working on an ERC1155 smart contract
- Finalized unit tests for block execution invariant
- Refactored transaction coordinator with arguments
- Ledger Nano S tests after deploying of the latest version.
- Added a response logger middleware on Elrond Proxy so we can have a better overview over failing requests
- Analyzed the runtime memory usage of the Elrond node.
- Worked on support for Testnet BTC on our fork of Trust Wallet Core (this feature will be used on Maiar).
- Fixed a concurrency issue on Observers, within the VM Querying components
- Sketched a Python prototype for trivial secret splitting (involving one-time pads and basic modular arithmetic) - could be useful for Maiar in the future.
- Working on automatic elrond-sdk docs publishing
- Investigate failed relayed TXs from the backend.
- Refactored API resolvers and adapted the latest changes in economics to the soft restart feature branch.
- Create logs parsing tool for bad transactions and used it to identify/debug some user registration failures in Maiar.
- Started to improve overall error logging in elrond-go
- Work on TransactionConverter to replace function references in other components
- Tested different branches to ensure compatibility & protocol overall quality
- Implemented a disabled node facade for the new API refactoring & the unit tests to ensure code coverage
- Working on chainlink - aggregator smart contract
- Continue to working on the task to move all the elastic indexer code in a new repository
@ElrondNetwork ecosystem. Check our progress & get involved 👇
https://t.co/YOoeEN0RIF
More from Business
You May Also Like
Curated the best tweets from the best traders who are exceptional at managing strangles.
• Positional Strangles
• Intraday Strangles
• Position Sizing
• How to do Adjustments
• Plenty of Examples
• When to avoid
• Exit Criteria
How to sell Strangles in weekly expiry as explained by boss himself. @Mitesh_Engr
• When to sell
• How to do Adjustments
• Exit
1. Let's start option selling learning.
— Mitesh Patel (@Mitesh_Engr) February 10, 2019
Strangle selling. ( I am doing mostly in weekly Bank Nifty)
When to sell? When VIX is below 15
Assume spot is at 27500
Sell 27100 PE & 27900 CE
say premium for both 50-50
If bank nifty will move in narrow range u will get profit from both.
Beautiful explanation on positional option selling by @Mitesh_Engr
Sir on how to sell low premium strangles yourself without paying anyone. This is a free mini course in
Few are selling 20-25 Rs positional option selling course.
— Mitesh Patel (@Mitesh_Engr) November 3, 2019
Nothing big deal in that.
For selling weekly option just identify last week low and high.
Now from that low and high keep 1-1.5% distance from strike.
And sell option on both side.
1/n
1st Live example of managing a strangle by Mitesh Sir. @Mitesh_Engr
• Sold Strangles 20% cap used
• Added 20% cap more when in profit
• Booked profitable leg and rolled up
• Kept rolling up profitable leg
• Booked loss in calls
• Sold only
Sold 29200 put and 30500 call
— Mitesh Patel (@Mitesh_Engr) April 12, 2019
Used 20% capital@44 each
2nd example by @Mitesh_Engr Sir on converting a directional trade into strangles. Option Sellers can use this for consistent profit.
• Identified a reversal and sold puts
• Puts decayed a lot
• When achieved 2% profit through puts then sold
Already giving more than 2% return in a week. Now I will prefer to sell 32500 call at 74 to make it strangle in equal ratio.
— Mitesh Patel (@Mitesh_Engr) February 7, 2020
To all. This is free learning for you. How to play option to make consistent return.
Stay tuned and learn it here free of cost. https://t.co/7J7LC86oW0
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.