Transaction hash is changed to lower case
complete
Arty
Transaction Hash is changed to lower case even though some blockchains have case-sensitive hashes (eg. Solana)
P
Petur
An update on transaction hashes for Solana:
Hashes will now be added to the transaction description since this field allows for case-sensitive strings. Previously synced transactions will not have this description so the only way to get the txHash description for all transactions in the wallet would be to recreate the wallet itself.
P
Petur
complete
transaction hashes will no longer be downcased for case-sensitive blockchains, such as Solana and Algorand.
Note that this fix will only affect transactions that are synced today or later. It will not change the hashes for any previously synced transactions
Y
Yellow Caribou
M
Multiple Narwhal
I don't understand why it can't be fixed the correct way and resync past transactions to get the proper hash addresses into every transaction.
G
Given Cockroach
@Petur. Putting the Tx Hash in the description field is better than nothing. However, why didn't you make your Tx Hash column case sensitive? This seems like a really kludgy fix. It would be so much better if we could click on the Tx Hash like with transactions for other chains and have it take us directly to the corresponding block explorer. Hopefully this was only a stop-gap solution and you plan to add this in the future.
B
Brave Stoat
Given Cockroach: 100% , agree with you
B
Blue Finch
Given Cockroach: 100% agree. Would be great if Solana tx hashes would link to solscan.io
F
Flying Porpoise
Given Cockroach: I wonder how costly it would be to update the column to be case sensitive. Not knowing their stack, where the txn information is stored, or how their code handles the txn information....
If this data is on a relational database and the field is some case insensitive type, then a safe migration would require creating a new case sensitive field and then backfilling it. And after the backfill is done, updating the code base to point to the new column.
Updating the existing column's type or renaming a column tend to be locking operations.
On most recent versions of Postgres, a type change from
citext
to text
is not locking as long as there is no index on the column. Again, just speculating their data and stack set-up.I imagine they have a lot of records, which would make any migration which locks very costly.
Not making any excuses for their decisions, but I imagine this isn't exactly an easy or quick fix and thus something they will need to budget for.
P
Petur
An update on transaction hashes for Solana:
Hashes will now be added to the transaction description since this field allows for case-sensitive strings. Previously synced transactions will not have this description so the only way to get the txHash description for all transactions in the wallet would be to recreate the wallet itself.
P
Petur
Merged in a post:
Transaction ID hashes are being converted to lowercase. Should remain in original case.
I
Ideal Hare
In the transactions page, all transaction hashes in the details tabs are being converted to lowercase. This means that a copy paste into a blockchain explorer will not find the transaction. These should remain in the original character case.
R
Red Bass
Huge pain! a link to a block explorer would also be much much appreciated
B
Brave Stoat
Yes this sucks and they are taking ages to fix it...
R
Rose Buzzard
Hi. My experience differs, however. Mintscan, to use just one example, is not case sensitive. I just tried several of my transactions and they are readily found both as upper case strings and as lower case strings.
B
Brave Stoat
YES. Huge issue!
Load More
→