User Details
- User Since
- Sep 4 2021, 00:53 (133 w, 5 d)
Yesterday
Wed, Mar 27
Tue, Mar 26
computer says no
Error workflow:
- Open Send and observe the camera auto opens as expected (since the config toggle is true)
- Toggle the auto open camera config to false
- Open Send and observe camera does not auto open
- Toggle the auto open camera config to true
- Open Send and the camera does not auto open again
- Despite refreshing app a few times, camera still does not auto open with the config set to true.
Mon, Mar 25
Tested ok, just a minor nit in function comments
Sun, Mar 24
It's not immediately clear whether each notification is an error, success or warning message at a quick glance. I would suggest using either a green tick/red cross/yellow exclamation mark to accompany each notification (via the icon prop) or customize the background color depending on the nature of the message. White text on black bg can be interpreted in different ways.
Sat, Mar 23
Fri, Mar 22
Much better
Error workflow:
- 100 XEC airdrop for 1c6c9c64d70b285befe733f175d0f384538576876bd280b10587df81279d3f5e, which should give you the following:
Tested all ok but it looks really out of place with the thick border
Thu, Mar 21
I'm seeing a perma-lock on incognito mode (which has no existing wallet in storage).
- No errors in console.
- Already tried npm ci.
- Reloaded and hard-refreshed multiple times.
Likely the cashtabLoaded state var isn't being set in the onboarding process?
I'll ping you on tg to whitelist my IP. Given the changes it would be good if I can manually test the token creation process in case there's something not obvious to the int tests coverage.
Tue, Mar 19
Starting to see 120,000 ms being exceeded
Is there a difference between an unknown token vs an invalid token that does not conform to SLPv1 or ALP standards?
Sat, Mar 16
Updated prefix reservation
If you toggle Send Confirmations in config to true, then send a normal XEC tx, that setting resets to false after tx broadcast.
Fri, Mar 15
Edge case: Send a token tx where you're sending the entire remaining token balance so that it needs to automatically route out of the SendToken.js and back to Home. The following bad state use warning is shown:
Wed, Mar 13
So my steps were:
- Deploy v2.0.10 to netlify
- Create new wallet on there
- Bump version to v2.0.11, then redeploy to netlify
- Waited around with the wallet open but no modal.
- Closed and re-opened browser, upgrade modal shows up on load
- Click OK, cashtab refreshes but Configure.js is still showing v2.0.10
Tue, Mar 12
Sat, Mar 9
Updated wed/extension logos and wording.
Fri, Mar 8
Manual testing observations:
- When switched to another wallet, the wallets[0] is updated but the separate wallet object is still on the previous wallet. Deleting this stale wallet in the wallet object does not update it.
- No longer seeing that edge case where clicking Activate on another wallet loops back to the same wallet, until you click Activate a 2nd time
- Wallet switching is soooo much faster now
Thu, Mar 7
Wed, Mar 6
Error: Cannot find module '../../mock-chronik-client/mocks/mockChronikResponses'
Require stack:
- /work/apps/examples/test/sendXec.test.js
Just so I'm clear on the underlying use case here, will this be used to parse through all tx history of the address to figure out whether the address has received this token at least once in its entire history, or is it to determine the user is currently holding a balance of this tokenId? If it's the latter then you can just use the etoken-list lib can't you?
Tue, Mar 5
accepted with note
I assume txs like this self minting tx are out of scope for this token server right? The function will return false as the minter won't be in the inputs but I guess this wouldn't be generated out of cashtab anyway yea?
Sun, Mar 3
Sat, Mar 2
Fri, Mar 1
Thu, Feb 29
- I can see the reasoning for getting rid of token ID is because it's not in chronik-client's genesisInfo, but why are the other properties grouped together in index [1]? Isn't it simpler to have them as individual props? Is there a performance/caching consideration here?
This might actually drive up a price market for grump tokens lol