I minted Frontline on @osura_com
If you are like me and didn't take part in the shitcoins shitshow on Ordinals lately but you are interested about art on Bitcoin, Frontline looks like a great opportunity to get some exposure to the space.
That would also mean you ain't familiar with the mint process of an ordinal... I'll share the two things that are different on BTC ordinals (compared to mints on Ethereum).
You have two addresses in the same account
One is for your BTC tokens holding, it usually starts with a 3..., the other one is where your ordinals will stay (it also holds some BTC because after all Ordinals are no more than sats (BTC cents) with an inscription on the Tx data)
This impacts you in two ways, the BTC to pay for the mint needs to be held on your BTC account. When you mint, the ordinal will be sent to your Ords account. This particularity, as pointed out by @blockpalette in the @OnChainMonkey holders channel, is to separate your BTC with non inscribed sats, from the ones with an inscription (imagine sending someone some BTC and ending up sending a valuable inscription in the process)
You need patience
That one is probably more obvious if you have ever transacted with the Bitcoin blockchain before, block time there is in minutes (from 10 to 60 on average). Don't be surprised if you still see your BTC on your wallet after you got a confirmation.... The block takes time to be brewed.
For frontline, you'll also need to wait extra days (non blockchain technology related) as the drop will happen on Monday. Practically you can think of this mint as a presale.
The positives ?
The Tx fee were quite low here... I paid 1$ ๐คฏ
You get an on chain inscription of piece of art in the most secure blockchain to date ๐ค๐ผ
Rendez vous ce jeudi 06 Juin pour dรฉcouvrir @spacehuntrs , un explore to earn vous permettant dโรชtre le pilote dโun vaisseau IA qui pourrait changer votre vie ๐
Curious to know how #CodeNewbies setup their user authentication system when building a new soft nowadays ?
Let us know in the comments, we might find a common pattern and build a tool around it ๐ป
Gm #web3โโ
Calling the following explorers:
@jsigwart@FaevsKij@Mackmental666@CHeco_nft@RisaBSchonbaum@ShaiGayadien@TomRoach234264@bencrypto123
We know we took time to be ready for this phase. We might even be mentioning an abandoned X account ๐
If you are still active and interested to mint your spot, reply with a ๐ซก
Here is a recap of the mint:
- 44 tokens guaranteed to 44 wallets
- Ethereum L1
- 0.022 ETH per token
Benefits on https://t.co/cEDH8VCOVk
With no reaction before tomorrow EOD, we might recycle your spot and grant it to somebody else.
Thank you ๐๐ผ
@etherscan any issue with the contract verification endpoint on Sepolia testnet ? ๐
We've been trying to get a contract verified for almost an hour but we keep on getting the "Pending in Queue" status for our verification request.
Please help ๐๐ผ
Quick @spacehuntrs#buildinpublic update ๐จ
1. a) The smart contract for the OG collection has been finalized and went through three rounds of QA, bugs and gas fees optimizations were done at each iteration. Security wasn't compromised either. Last QA round is *hopefully* being done today ๐ค๐ผ
b) The webUI to mint the tokens has also been built and went through QA already
2. a) The ECCs minigame backend was developed and is going to be QA'd next
b) most visual assets have been created and have been built using threejs/webGL
3. Currently building the mini game qualifications layer (to stop relying on broken third parties to check activity on X)
If you are curious to know how we are laying the technical foundations of the game, read ๐๐ผ
- SC in Solidity using forge for automated tests, gas reports and deployment scripts
- ECCs minigame is an Event Driven microservice built in @elixirlang and communicates with the main GQL gateway through a mix of PgSQL Listen/Notify (for the eventStore) and PubSub
- The qualifications layer is embedded inside the GQL gateway and leverages a smart queue mechanism to push back twitter requests that can fail because of the low API rate limits they impose. It also provide observability, so we can adjust the API sub if the queue is too full (that's a problem I wish we'll have ๐)
- WebUIs are mobile first and built on NuxtJS (VueJS)
- Wallet connection relies on Metamask (we are still facing some issues on mobile here)
- Connection is through a wallet signature (no Tx) and players will be notified through web Push notifications (if they wish to stay fully anonymous) or via email
- We used three external webservices that were internally built and lets us easily manage user accounts, page building and all types of notifications.
I'm working hand in hand ๐ค๐ผ with the @_GeeksSolutions team to deliver a great product ๐ค๐ผ
Hit me up below if you have comments, questions or you simply want to cheer us up