Great news! 49 out of 50 US states are now able to buy $ZIL directly through www.crypto.com ๐
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
๐บ๐ธ๐บ๐ธ๐บ๐ธ๐บ๐ธ
You can now transfer your $ZIL stake from one wallet to another without going through the unbonding period.
๐ http://stake.zilliqa.com
๐ http://stake.zilliqa.com
This media is not supported in your browser
VIEW IN TELEGRAM
ZilSwap Lightning season 4 starts on Wednesday!๐ณ๏ธ
Tier 1 pools: $gZIL, $XSGD
Tier 2 pools: $PORT, $SCO, $CARB, $ZLP, $XCAD, $ZCH, $Elons
Tier 3 pools: $STREAM, $GARY, $SRV, $ZYRO, $REDC, $ZLF, $DUCK, $MAMBO, $MESSI
Vote nowโก๏ธ https://vote.zilliqa.com/#/zwap/active
Tier 1 pools: $gZIL, $XSGD
Tier 2 pools: $PORT, $SCO, $CARB, $ZLP, $XCAD, $ZCH, $Elons
Tier 3 pools: $STREAM, $GARY, $SRV, $ZYRO, $REDC, $ZLF, $DUCK, $MAMBO, $MESSI
Vote nowโก๏ธ https://vote.zilliqa.com/#/zwap/active
ZIL-ETH bridge is all set to enable cross-chain interoperability and adoption. Details below!
As youโre well aware, weโre working on creating blockchain interoperability through construction of a ZIL-ETH Bridge. This massive project has been a joint undertaking between the Zilliqa, Switcheo and Polynetwork teams, each of whom are committed to the cause of contributing to a true DeFi ecosystem.
There are myriad ways in which this bridge will help you, and we tell you all about it in our latest post:
https://bit.ly/35OYQQg
๐คทโโ๏ธTL;DR
โญ๏ธTestnet is expected to go live for beta testing in about 10 days. Weโll be offering some discretionary $ZIL rewards for those providing constructive feedback on UX/UI and technical bugs. Stay tuned on the testnet launch date!
โญ๏ธWeโve set up an incentive mechanism for mainnet liquidity providers for cross-chain assets.
โญ๏ธSneak peeks of the bridge flow UI/UX included.
โญ๏ธWork on ERC20 ZIL token swap will start after bridge mainnet launch in Q3 2021.
As youโre well aware, weโre working on creating blockchain interoperability through construction of a ZIL-ETH Bridge. This massive project has been a joint undertaking between the Zilliqa, Switcheo and Polynetwork teams, each of whom are committed to the cause of contributing to a true DeFi ecosystem.
There are myriad ways in which this bridge will help you, and we tell you all about it in our latest post:
https://bit.ly/35OYQQg
๐คทโโ๏ธTL;DR
โญ๏ธTestnet is expected to go live for beta testing in about 10 days. Weโll be offering some discretionary $ZIL rewards for those providing constructive feedback on UX/UI and technical bugs. Stay tuned on the testnet launch date!
โญ๏ธWeโve set up an incentive mechanism for mainnet liquidity providers for cross-chain assets.
โญ๏ธSneak peeks of the bridge flow UI/UX included.
โญ๏ธWork on ERC20 ZIL token swap will start after bridge mainnet launch in Q3 2021.
Media is too big
VIEW IN TELEGRAM
Together with Zillacracy we are launching a new community-driven education portal on all things blockchain. All of us can now start spreading news and educate the world about Zilliqa & blockchain technology in all different languages ๐งโ๐
What are some examples of what you can do?
๐๏ธ You can now read or create content about the latest blockchain news in your own language
๐ฑ Start growing your following for your personal account or for your project/community/brand
๐ฐ Unlock $ZIL & merch by publishing high-quality content
๐ฃ Share content with others to get more people involved
& more
A community-driven education platform will allow individuals, brands, communities, and projects from all over the world to help create awareness about Zilliqa & blockchain technology. This will help grow the $ZIL ecosystem as a whole and allow Learn Blockchain to become one of the foundational education platform within the crypto space. Together we can make this possible!
Click here to learn more โก๏ธ https://bit.ly/3h3KQZq
What are some examples of what you can do?
๐๏ธ You can now read or create content about the latest blockchain news in your own language
๐ฑ Start growing your following for your personal account or for your project/community/brand
๐ฐ Unlock $ZIL & merch by publishing high-quality content
๐ฃ Share content with others to get more people involved
& more
A community-driven education platform will allow individuals, brands, communities, and projects from all over the world to help create awareness about Zilliqa & blockchain technology. This will help grow the $ZIL ecosystem as a whole and allow Learn Blockchain to become one of the foundational education platform within the crypto space. Together we can make this possible!
Click here to learn more โก๏ธ https://bit.ly/3h3KQZq
Curious about whatโs the optimal restaking period for you to maximise your returns on staked $ZIL?
Check out this article by our community member Kamran on our LearnBlockchain.org educational portal!
Here are some key takeaways from the article
- If you stake less than 3,662 $ZIL claiming more than once a year results in a loss (due to fees)
- Claiming in random intervals (i.e. 7 or 30days) vs optimised periods (i.e. daily) results in a huge difference w large amounts(16mil in the example)
- For around 1M $ZIL the optimum claim and restake cycle is at 7 days giving you the max returns
- Optimise your claiming schedules if your goal is to accumulate more $gZIL
This is just the condensed version of what the article states, to get a better understanding of how these calculations come about and the assumptions made, we suggest you read the article. The article is definitely insightful and will help you in deciding on when to compound for you to optimise your $ZIL and $gZIL gains!
https://learnblockchain.org/4763/zilliqa-staking-a-claim-staking-compounding-optimization-idea/
Check out this article by our community member Kamran on our LearnBlockchain.org educational portal!
Here are some key takeaways from the article
- If you stake less than 3,662 $ZIL claiming more than once a year results in a loss (due to fees)
- Claiming in random intervals (i.e. 7 or 30days) vs optimised periods (i.e. daily) results in a huge difference w large amounts(16mil in the example)
- For around 1M $ZIL the optimum claim and restake cycle is at 7 days giving you the max returns
- Optimise your claiming schedules if your goal is to accumulate more $gZIL
This is just the condensed version of what the article states, to get a better understanding of how these calculations come about and the assumptions made, we suggest you read the article. The article is definitely insightful and will help you in deciding on when to compound for you to optimise your $ZIL and $gZIL gains!
https://learnblockchain.org/4763/zilliqa-staking-a-claim-staking-compounding-optimization-idea/
Zilliqa Monthly Newsletter - June 2021
In what was a choppy month for the cryptosphere in general, Zilliqa kept building, with progress being made to its ecosystem and new campaigns launching and flourishing.
Some of the highlights include
- Zilliqa Football Stars campaign accomplishmentsโฝ๏ธ
- ZILSwap ZILO for $STREAM Token๐
- ZILHiveโs NFTs Made Easy Hackathon
๐ Bull or ๐ป Bear, we keep building. ๐๐
Read more here
https://blog.zilliqa.com/zilliqa-monthly-newsletter-june-2021-8e2de2239510
In what was a choppy month for the cryptosphere in general, Zilliqa kept building, with progress being made to its ecosystem and new campaigns launching and flourishing.
Some of the highlights include
- Zilliqa Football Stars campaign accomplishmentsโฝ๏ธ
- ZILSwap ZILO for $STREAM Token๐
- ZILHiveโs NFTs Made Easy Hackathon
๐ Bull or ๐ป Bear, we keep building. ๐๐
Read more here
https://blog.zilliqa.com/zilliqa-monthly-newsletter-june-2021-8e2de2239510
Medium
Zilliqa Monthly Newsletter โ June 2021
Bull or Bear, We Continue On Building Strong
ZILBridge Beta Testing Now Open to the Community!
โญ๏ธStart using the much-awaited bridge and share your feedback on UX/UI and tech in exchange for exciting $ZIL Rewards from 8-22 July. Reward pool worth US$5000!
โญ๏ธGet started by interacting with the UI on zilswap.io/bridge . Play around with the supported tokens ETH, ZIL, ZWAP, DAI today! Refer to the step-by-step instructions on how to get testnet ZIL, compatible wallets and tokens and everything else here. https://docs.zilswap.io/how-to/zilbridge/beta-testing
โญ๏ธFeedback Form: https://forms.gle/SeUHjA1ySAZs6GQYA. Remember to be as specific as possible with your comments and suggestions. Happy Bridging! โฆโโโโโโฆ
โญ๏ธStart using the much-awaited bridge and share your feedback on UX/UI and tech in exchange for exciting $ZIL Rewards from 8-22 July. Reward pool worth US$5000!
โญ๏ธGet started by interacting with the UI on zilswap.io/bridge . Play around with the supported tokens ETH, ZIL, ZWAP, DAI today! Refer to the step-by-step instructions on how to get testnet ZIL, compatible wallets and tokens and everything else here. https://docs.zilswap.io/how-to/zilbridge/beta-testing
โญ๏ธFeedback Form: https://forms.gle/SeUHjA1ySAZs6GQYA. Remember to be as specific as possible with your comments and suggestions. Happy Bridging! โฆโโโโโโฆ
๐1
๐ ALL INVITED TO THE PARTY OF THE YEAR: SAVE THE DATE FOR ZIL4
Zilliqans, it's that time of the year again! We're all set to celebrate our 4th Birthday in style.๐
This year's all-virtual ZIL4 will bring together our top minds, ecosystem partners and ZILHive stars via Youtube.
๐ Save the Date: 30 July, 10pm SGT.
Details on themes and speakers to come shortly. Follow us on Twitter (@zilliqa) and Telegram for more.
Zilliqans, it's that time of the year again! We're all set to celebrate our 4th Birthday in style.๐
This year's all-virtual ZIL4 will bring together our top minds, ecosystem partners and ZILHive stars via Youtube.
๐ Save the Date: 30 July, 10pm SGT.
Details on themes and speakers to come shortly. Follow us on Twitter (@zilliqa) and Telegram for more.
Dear Community,
The network is currently down. Our team is quickly working to resolve the issue.
We will update you once the issue is solved. We apologise for any inconvenience caused!
As always, your funds remain SAFU.
The Zilliqa Team
The network is currently down. Our team is quickly working to resolve the issue.
We will update you once the issue is solved. We apologise for any inconvenience caused!
As always, your funds remain SAFU.
The Zilliqa Team
Zilliqa Announcement
Dear Community, The network is currently down. Our team is quickly working to resolve the issue. We will update you once the issue is solved. We apologise for any inconvenience caused! As always, your funds remain SAFU. The Zilliqa Team
Dear community,
We have noticed that several nodes in the network have gone out of memory after we introduced a new memory limit management in the network recovery that occurred an hour ago. We are 1) conducting a re-recovery of the network 2) removing the management limit and 3) increasing the node memory to mitigate this issue.
We sincerely apologize for the inconvenience caused.
We have noticed that several nodes in the network have gone out of memory after we introduced a new memory limit management in the network recovery that occurred an hour ago. We are 1) conducting a re-recovery of the network 2) removing the management limit and 3) increasing the node memory to mitigate this issue.
We sincerely apologize for the inconvenience caused.
๐1
Dear community members,
We have noticed memory management with regards to processing very large smart contracts. We are temporarily disabling transaction processing within the mainnet. Blocks will be produced with 0 transaction.
We will implement the fix and upgrade the mainnet in the next 24 hours to resolve the issue.
For the more technical folks, this issue is a result of memory fragmentation, which in turn unable to return memory to the kernel. If you are interested, here is a good blog article we found to explain the issue.
https://www.algolia.com/blog/engineering/when-allocators-are-hoarding-your-precious-memory/
We have noticed memory management with regards to processing very large smart contracts. We are temporarily disabling transaction processing within the mainnet. Blocks will be produced with 0 transaction.
We will implement the fix and upgrade the mainnet in the next 24 hours to resolve the issue.
For the more technical folks, this issue is a result of memory fragmentation, which in turn unable to return memory to the kernel. If you are interested, here is a good blog article we found to explain the issue.
https://www.algolia.com/blog/engineering/when-allocators-are-hoarding-your-precious-memory/
Algolia
When allocators are hoarding your precious memory
โฆ
๐1
Dear everyone,
Thank you for your patience while transactions processing is disabled on Zilliqa mainnet.
As part of the fix to resolve the large memory consumption on the mining nodes for DS Committee, we will be conducting a network upgrade to version tag
Do note that during the upgrade period no transactions will be processed by the network and blockchain API may not be accessible.
Thank you for your continued support!
Thank you for your patience while transactions processing is disabled on Zilliqa mainnet.
As part of the fix to resolve the large memory consumption on the mining nodes for DS Committee, we will be conducting a network upgrade to version tag
v8.0.5 at block number 1283088. This upgrade is likely to take place around 14 July 6.45 AM UTC. For more information on this urgent upgrade, please refer to the release note at Zilliqa v8.0.5 release notes (https://github.com/Zilliqa/Zilliqa/releases/tag/v8.0.5)Do note that during the upgrade period no transactions will be processed by the network and blockchain API may not be accessible.
Thank you for your continued support!
GitHub
Release v8.0.5 ยท Zilliqa/Zilliqa
This hotfix addresses a high memory consumption in regards to processing very large smart contracts. (#2650)
Dear community members,
The mainnet urgent upgrade of v8.0.6 has been completed (14 July 2021 11:20 UTC). As part of this urgent upgrade, we fixed an issue that can cause mining node to go out of memory. Release note is at https://github.com/Zilliqa/Zilliqa/releases/tag/v8.0.6
We apologize for the inconvenience caused.
The mainnet urgent upgrade of v8.0.6 has been completed (14 July 2021 11:20 UTC). As part of this urgent upgrade, we fixed an issue that can cause mining node to go out of memory. Release note is at https://github.com/Zilliqa/Zilliqa/releases/tag/v8.0.6
We apologize for the inconvenience caused.
GitHub
Release v8.0.6 ยท Zilliqa/Zilliqa
This hotfix addresses a high memory consumption in regards to processing very large smart contracts on dsguards (#2650) and normal node (#2652)
4 YEARS. 5 THEMES. INFINITE POSSIBILITIES: DISCOVER MORE ON 30 JULY! 4๏ธโฃ๐ฅณ๐๐
The countdown for our 4th B'day celebrations begins! Join us live on Youtube, 30 July, 10PM SGT to learn how the Zilliqa ecosystem is BUIDLing and thriving.
We'll talk about our milestones and vision across 5 core segments, all of which come under the #ZIL4ALL umbrella theme.
Can't wait to celebrate with you all!
The countdown for our 4th B'day celebrations begins! Join us live on Youtube, 30 July, 10PM SGT to learn how the Zilliqa ecosystem is BUIDLing and thriving.
We'll talk about our milestones and vision across 5 core segments, all of which come under the #ZIL4ALL umbrella theme.
Can't wait to celebrate with you all!
Dear all,
The last major upgrade v8.0 (https://github.com/Zilliqa/Zilliqa/releases/tag/v8.0.0) was feature packed. It reduced the block time, revised the consensus protocol, introduced remote state reads for Scilla, adjusted priorities for new miners, and included several other core optimizations and bug fixes. However, since that upgrade, the network has at times become unstable. This has required the core team to intervene on several occasions to introduce patches, resulting in unwanted network downtime.
We understand the frustration and inconvenience that the upgrade has caused to token holders, exchanges, wallet providers, miners and other relevant parties. The intention of this post is to share details around this topic, our general development and testing process to bring transparency to you all and steps we plan to take to reduce the chances of such events as we move forward.
As you already know, the underlying tech at Zilliqa is cutting-edge and we are constantly innovating and adding new features to the protocol. Our approach to introducing these new features follows established industry-standards of writing unit tests and running correctness and stress tests. Once the changes and unit tests are fully ready, we run these new changes on a private small-scale network for a period of time, followed by a large-scale integration at the mainnet-scale and then deploy the changes on a public testnet open for all to interact with. If a bug is found during testing on any of the networks, the bug is fixed and we start from the first step, by writing a unit test to capture the bug, deploying the fixes on a private network and so on.
Many of these cutting-edge innovations in engineering and development however present a key challenge. Until these changes go live on a production mainnet system, it is impossible to be certain that the introduced changes are free of bugs. While we discourage testing anything in production, sometimes it is clear that the real test is always in production.
We would also like to highlight that some issues are beyond our codebase and control as there could be dependencies on external systems, libraries and infrastructures. The most recent memory issue is a good example of this (https://www.algolia.com/blog/engineering/when-allocators-are-hoarding-your-precious-memory/). In many cases, we are forced to push a fix upstream to well known open source packages or have a workaround if there is no viable solution.
Guaranteeing that a given piece of software is free of bugs is close to impossible but we certainly try to ensure that. Despite these challenges, we are committed to constantly innovate and add new features to the chain with minimal disruption and bugs.
To this end and given the recent downtime, we are also taking our testing process a step further, by using formal verification tools to model the system and formally verify the generated model and whenever possible the implementation. Even though formal verification tools require extensive man hours, they are extremely helpful in verifying correctness, reliability and dependability of mission critical software systems. The goal is to combine unit testing and formal verification which complement each other in detecting any design or implementation issues with critical parts of the codebase. In order to mitigate the issues further, we are planning to reduce the frequency of the network upgrade that contains new features which will give more time for the network to test features in the wild. We will also reduce the number of features that will go in a given release to minimize the size of the new code that gets exposed.
The last major upgrade v8.0 (https://github.com/Zilliqa/Zilliqa/releases/tag/v8.0.0) was feature packed. It reduced the block time, revised the consensus protocol, introduced remote state reads for Scilla, adjusted priorities for new miners, and included several other core optimizations and bug fixes. However, since that upgrade, the network has at times become unstable. This has required the core team to intervene on several occasions to introduce patches, resulting in unwanted network downtime.
We understand the frustration and inconvenience that the upgrade has caused to token holders, exchanges, wallet providers, miners and other relevant parties. The intention of this post is to share details around this topic, our general development and testing process to bring transparency to you all and steps we plan to take to reduce the chances of such events as we move forward.
As you already know, the underlying tech at Zilliqa is cutting-edge and we are constantly innovating and adding new features to the protocol. Our approach to introducing these new features follows established industry-standards of writing unit tests and running correctness and stress tests. Once the changes and unit tests are fully ready, we run these new changes on a private small-scale network for a period of time, followed by a large-scale integration at the mainnet-scale and then deploy the changes on a public testnet open for all to interact with. If a bug is found during testing on any of the networks, the bug is fixed and we start from the first step, by writing a unit test to capture the bug, deploying the fixes on a private network and so on.
Many of these cutting-edge innovations in engineering and development however present a key challenge. Until these changes go live on a production mainnet system, it is impossible to be certain that the introduced changes are free of bugs. While we discourage testing anything in production, sometimes it is clear that the real test is always in production.
We would also like to highlight that some issues are beyond our codebase and control as there could be dependencies on external systems, libraries and infrastructures. The most recent memory issue is a good example of this (https://www.algolia.com/blog/engineering/when-allocators-are-hoarding-your-precious-memory/). In many cases, we are forced to push a fix upstream to well known open source packages or have a workaround if there is no viable solution.
Guaranteeing that a given piece of software is free of bugs is close to impossible but we certainly try to ensure that. Despite these challenges, we are committed to constantly innovate and add new features to the chain with minimal disruption and bugs.
To this end and given the recent downtime, we are also taking our testing process a step further, by using formal verification tools to model the system and formally verify the generated model and whenever possible the implementation. Even though formal verification tools require extensive man hours, they are extremely helpful in verifying correctness, reliability and dependability of mission critical software systems. The goal is to combine unit testing and formal verification which complement each other in detecting any design or implementation issues with critical parts of the codebase. In order to mitigate the issues further, we are planning to reduce the frequency of the network upgrade that contains new features which will give more time for the network to test features in the wild. We will also reduce the number of features that will go in a given release to minimize the size of the new code that gets exposed.
GitHub
Release v8.0.0 ยท Zilliqa/Zilliqa
This major release will introduce new features such as reduced block time, revised consensus protocol, remote state read for Scilla, priority adjustments for new miners, payment transaction fee inc...
Part 2)
On a separate but somewhat (un)related note, while troubleshooting the latest bug, we happened to notice a couple of smart contracts deployed on the mainnet where the implemented logic makes the contract state grow with new transactions. As a fix, we are going to fine tune some of the parameters which are currently set that allows the underlying design patterns to go unnoticed during development and testing. Better static and dynamic analysis tools will also help warn developers in this regard.
Do note that such contracts may work fine for now but may sooner or later hit the block gas limit, rendering these contracts uncallable. We encourage developers to be mindful of this and other similar design patterns. For example, if a contract is using a list and if that list grows with every single transaction, this may create issues in the future for the contract. Also, contracts should avoid loops whenever possible as loops on a very large list or map will hit the block gas limit at some point. Similarly, itโs advised to adopt a pull model instead of a push model, i.e., instead of a contract computing and distributing rewards to several users (push model), the contract should be designed in a way that each user could claim his own reward himself (pull model). Some relevant and useful tips on this and other design patterns around smart contract development can be found here: https://scilla.readthedocs.io/en/latest/scilla-tips-and-tricks.html# and https://docs.soliditylang.org/en/v0.4.24/common-patterns.html
Thank you for your understanding and your support. We will keep pushing ourselves to make Zilliqa a better and robust platform for all to use.
Sincerely,
The Zilliqa Team
On a separate but somewhat (un)related note, while troubleshooting the latest bug, we happened to notice a couple of smart contracts deployed on the mainnet where the implemented logic makes the contract state grow with new transactions. As a fix, we are going to fine tune some of the parameters which are currently set that allows the underlying design patterns to go unnoticed during development and testing. Better static and dynamic analysis tools will also help warn developers in this regard.
Do note that such contracts may work fine for now but may sooner or later hit the block gas limit, rendering these contracts uncallable. We encourage developers to be mindful of this and other similar design patterns. For example, if a contract is using a list and if that list grows with every single transaction, this may create issues in the future for the contract. Also, contracts should avoid loops whenever possible as loops on a very large list or map will hit the block gas limit at some point. Similarly, itโs advised to adopt a pull model instead of a push model, i.e., instead of a contract computing and distributing rewards to several users (push model), the contract should be designed in a way that each user could claim his own reward himself (pull model). Some relevant and useful tips on this and other design patterns around smart contract development can be found here: https://scilla.readthedocs.io/en/latest/scilla-tips-and-tricks.html# and https://docs.soliditylang.org/en/v0.4.24/common-patterns.html
Thank you for your understanding and your support. We will keep pushing ourselves to make Zilliqa a better and robust platform for all to use.
Sincerely,
The Zilliqa Team
Forwarded from UFF Sports Announcements
Media is too big
VIEW IN TELEGRAM
Retired CFL Hall of Famer Nik Lewis โ now a Digital Athlete NFT with UFF Sports โ wants you to join him for the UFAFL Franchise Auction, July 16-18 in Las Vegas, to launch the Ultimate Fantasy American Football League.
To register for the auction, go to www.uffsports.com/ufafl and then email info@uffsports.com to become a verified bidder.
โIf you want the most in-depth, high stakes fantasy experience that feels like youโre running an NFL front office, then you need to register now to bid on one of these franchises,โ said UFFS head of football operations Andy McNamara. โBecome part of the fantasy revolution.โ
For more information on UFFS, visit www.uffsports.com
To register for the auction, go to www.uffsports.com/ufafl and then email info@uffsports.com to become a verified bidder.
โIf you want the most in-depth, high stakes fantasy experience that feels like youโre running an NFL front office, then you need to register now to bid on one of these franchises,โ said UFFS head of football operations Andy McNamara. โBecome part of the fantasy revolution.โ
For more information on UFFS, visit www.uffsports.com
Forwarded from Larry Fisher
Itโs showtime! Andy McNamara and NFL great Eric Metcalf are live from Las Vegas, hosting the conclusion of the UFAFL Franchise Auction that will welcome 32 owners to the Ultimate Fantasy American Football League.
The Two Minute Warning will take effect at 4 p.m. ET, resetting the clock to 2 minutes with every bid. The auction ends when there are no bids for a full 2 minutes and the top 32 bidders become the new UFAFL franchise owners.
The leaderboard is crowded. The bidders are ready to rumble. Watch live on AO Sports: https://aosports338604838.wpcomstaging.com/ufafl-franchise-auction-live/
The Two Minute Warning will take effect at 4 p.m. ET, resetting the clock to 2 minutes with every bid. The auction ends when there are no bids for a full 2 minutes and the top 32 bidders become the new UFAFL franchise owners.
The leaderboard is crowded. The bidders are ready to rumble. Watch live on AO Sports: https://aosports338604838.wpcomstaging.com/ufafl-franchise-auction-live/
ZILHive has just officially concluded the 10th wave of grantees!
Included in the 10th wave of grantees are 10 exciting projects that will bring tremendous value to the Zilliqa Ecosystem
These projects include:
DeMons - The gamified, community-driven NFT metaverse collectible series
The Mishka - Integrated Augmented Reality NFT functionality on Zilliqa
ZilGAM - A generative art and music app that produces generative content
Read the blog below to find out more about all the grantees in this 10th wave of grants. Hereโs to building a vibrant and diverse Zilliqa ecosystem!๐๐
https://blog.zilliqa.com/celebrating-10-waves-of-zilhive-grants-awardees-f847cb271e29
Included in the 10th wave of grantees are 10 exciting projects that will bring tremendous value to the Zilliqa Ecosystem
These projects include:
DeMons - The gamified, community-driven NFT metaverse collectible series
The Mishka - Integrated Augmented Reality NFT functionality on Zilliqa
ZilGAM - A generative art and music app that produces generative content
Read the blog below to find out more about all the grantees in this 10th wave of grants. Hereโs to building a vibrant and diverse Zilliqa ecosystem!๐๐
https://blog.zilliqa.com/celebrating-10-waves-of-zilhive-grants-awardees-f847cb271e29
Medium
Celebrating 10 waves of ZILHive Grants awardees!
Greetings everyone,