emerald-dao / float Goto Github PK

I suggest you assign the flow-blockchain Github topic to this repository for easier discoverability by the community.

This has become the official Flow blockchain topic: https://github.com/topics/flow-blockchain

Here are the detail:

https://floats.city/0x66a76313af93e9ee/event/287707085
[Error Code: 1103] The account with address (66a76313af93e9ee) uses 100174 bytes of storage which is over its capacity (100000 bytes). Capacity can be increased by adding FLOW tokens to the account.

https://floats.city/0x78993d7e62c7015f/event/296436406
[Error Code: 1103] The account with address (78993d7e62c7015f) uses 100350 bytes of storage which is over its capacity (100000 bytes). Capacity can be increased by adding FLOW tokens to the account.

It is good to have "100" displayed to demonstrate the format of how people should input to it.
But sometimes confusing if the user can use it as a default number.

Suggested to change it to "e.g. 100"
Similar idea to secret code, can be "e.g. mySecretCode"

Please also remind the FLOAT Creator and Claimers the FLOAT code is case sensitive.

Hey,

Recently, when claiming a float, the following error often occurs:

As far as I understand, the problem is that there are not enough tokens on the account that pays transaction fee in the Flow blockchain.

But the problem is that there are some users who can't actually figure out what's going on. I've seen questions like: "Does this message mean, I have to deposit tokens to my Flow wallet?".

Do you think it's worth making this message more user-friendly so as not to scare non-technical users? For example, we could display something like: We are having technical problems, please try again later.

Create an official testnet branch with testnet contracts for debugging and testing (incl. for devs wanting to integrate with FLOATs)

While claiming, the claim button will show "successfully claim" no matter the claim is successful or not.

• Add support for .find and .fn search
• Show .find and/or .fn names as authors of FLOAT events
• Add special "verified" badging, either created internally via Emerald, or via find/flowns

Float should use Discovery API to show wallets

https://developers.flow.com/tools/fcl-js/reference/discovery

One of my Blocto wallets can't claim FLOAT, but I can create events normally.

That wallet is self-custodian mode and has performed a recovery process once, so it has 7 keys with 4 of them revoked

Would be nice if the table sort is default the recently received and created dates.
recently received date - So people can see which Floats they have just received. Since we don't have a notification system.
recently created date - So Float event creators can see which float they have just made.

Vite does not include node polyfills, so when upgrading FCL they need to be solved by the bundler.

• award to specific addresses
• close/open
• delete?

I'm an event admin and I've been trying to manually award a user's wallet to distribute a FLOAT to them. Our FLOAT was active through 4pm CST today, and I've trying to distribute subsequent to that. I first tried to distribute directly to Dapper wallet, then I had the user connect their Dapper wallet, then I created a whole new event and attempted to manually add a duplicate FLOAT to them that way. The transaction made it's way up to executed every time and then produced the error: "Error: Could not get the public FLOAT Collection from the recipient. | 47 | ?? panic("Could not get the public FLOAT Collection from the recipient.") | ^^^^^^^". I tried pausing and resuming claiming on both the initial and duplicate event, but continued to receive the error message nonetheless.

Tried to award manually to a bunch of people today, the csv file had addresses with 0x in them and these where stripped for some reason.

Tx that worked (from overflow) https://flowscan.org/transaction/b1387950ffe9bc7c8e28fd2cb55d0e9d83a5c15948cf00a00fd0c76a653d8cef/script

tx that failed
https://flowscan.org/transaction/8de9873a55c21ac3dbd1b43aba8b477699477cba45e7394a9f7029d8aca7f646

the addresses sent in in both cases where from the following file
0x0ccc515c9eb2db31,0x46d6fb10be71d261,0x4260ef47d4b44336,0x53eb546c815a91cc,0x02d84224d1aa318e,0x142935d2b08885bb,0xcee95bd7c5bd993a,0x22613f6a9fe740e8,0xcee95bd7c5bd993a,0x62c4557bf0e6f559,0xea6b3b9e8df9164e,0x47b1de37e8d86e29,0x91b508315be4545c,0x18d7e8fd44629257,0x51664caf2b7550ef,0x42f8becfea8d6c3b,0x57ba2117c1c7132b,0xaf8503b01cb78b2f,0xb40f0bef13757ef8,0xe54b9b714b15760c,0x5dea7a65de215c37,0x830c83654c015c76,0xa67143ef9c32b407,0x5fba88b1c1f692c4,0x33c221718d0b93ca,0xb8023f7992b2858d,0xeb2fa201fa3a8fad,0x1547db33067fdfd8,0x06a4104a9fd67dd6,0x58ce9dd1302b7941,0x4155bbb6d3a18803,0xd38e4d0b4ea7ae3d,0xc85a332060b51589,0x93d12322aa2f960b,0xeb219b354507ea7d,0xe6d95eb8a1356d19,0x25c28d063e66365e,0x4ecf6aaa3a6bfe3a