Thread by @feliperieger

Just to clarify, there is a misunderstanding outside again. There's no false narrative. I love what I do, this community, and this project, and I have no problem staying and clarifying if there are doubts outside. I think you deserve things clarified.

🧵 1/16

Some weeks ago, I received the request to make the INO from @LoveMonsterNFT. A project that started on another chain and wanted to migrate to #KleverChain. #KleverNFT platform was going to be launched soon, and they applied to list.

🧵 2/16

One of the requests and briefing was that the Collection is items from the game. That is, @LoveMonsterNFT HAD to Mint all the 9,999 #NFTs characters to have the game fully working. So, our team figured out this was a special event for the platform.

🧵 3/16

It would be a completely different experience, as we could not be using the on-chain tools and native SDK from #KleverChain for this event. We had to adapt the Launchpad for this and make it through another created API.

klever.gitbook.io/kleverchain-sd…

🧵 4/16

They had some demands to our team apply technically. They needed to move NFTs from the sale too:

- 500 NFTs for the game breed
- 49 NFTs to holders migrating to the chain

We created the feature on the API to adapt to it, and that's why there are 9,450 NFTs on sale.

🧵 5/16

The Launchpad is a service provider to projects. A platform that creates the INO, processing payments, helping projects to launch on the #web3. The platform does NOT OWN the inventory. They are from the Creator. We are a SERVICE provider. We execute the demands.

🧵 6/16

All is done under the creator wallet, the api handles with all the calls and transactions between the creator and the collectors using a Queue system.

🧵 7/16

During some minutes, our queue API received a large volume of requests, and some users started to click so many times on the Buy Button. Some payments failed because of a missing balance, and the API just saved the NFTs batches as pending to the user on the backend.

🧵 8/16

Every pending transaction is a click from the user on the Buy Button. To conclude the NFT transaction with the buy NFT order on this API model, you must fully Pay the creator (Love Monster) and the platform.

We solved the high demand issue, and the problem was over.

🧵 9/16

NFTs that are shown in your account with the status paid are yours. You can list them on Wednesday on the DEX Marketplace or withdraw. Users with a pending action under the account can finish the transaction on Monday.

🧵 10/16

It is up to the user to finish the payment or not through the API, as they have a pending transaction. I know that this is not #web3 experience, I agree with you. But this was the model the Launchpad found to adapt to this demand.

🧵 11/16

I Tweeted about the web2 experience at this event on Monday. Those users do not have the purchase concluded. It's like a web2 e-commerce because you have a pending invoice on your account. @LoveMonsterNFT is raising funds to BUILD the project.

🧵 12/16

I'm seeing Tweets that suggest Klever should give NFTs from Love Monster with pending payment in their account. Sorry guys, It doesn't make any sense at all. We can't break a transaction flow from a pending status. It was a tech issue only not a giveaway.

🧵 13/16

Sorry if you are one of the few affected. I ask your understanding to finish the transaction on Monday. You conclude and are done, NFT is yours. I don’t understand this noise because of an NFT that is pending payment.

🧵 14/16

I like clarity, values, and everything should be fair. On Monday, we can provide you with all the history if you are affected. Payments were made on the chain. If you did is there. If not… I helped some users involved, and it’s all good with them.

🧵 15/16

Fail? Check the volume.

What’s next?

- New INO model fully #web3 experience.🔥

- DEX Marketplace in 3 days.
- The collection has a great volume.
- Secondary market is promising.
- New projects coming.
- Need more creators, DM me.

Sorry to the affected. Lov ya💜

🧵 16/16