-
ma2bd updated
4 months ago
-
Currently, developing an app requires `near-primitives` to interact with the result types of transactions as `near-api` propagates them.
As for me, it's pretty inconvenient, and would be better if …
-
Both packages fail the xltest both of which create an insanely large (lazy) input to hash. It was observed that the Eta process quickly went from 1.0GB -> 2.0GB memory usage within a matter of 20 seco…
-
Class 'com.appmattus.crypto.Algorithm' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.0.0, expected version is 1.8.0.
The class is loaded from C:/Users/s…
-
The choice between `safe` and `unsafe` is not really something the tool can make on behalf of the user, though in the absence of any configuration, `safe` should be the default. There are also exampl…
edsko updated
3 months ago
-
I noticed that yesod depends on skein (via clientsession) and cryptohash (via yesod-auth). Meanwhile, since cryptohash is deprecated, I use cryptonite in my code. Resulting in a binary containing seve…
joeyh updated
7 years ago
-
A common use case on NEAR is to deploy the same smart contract many times on many different accounts. For example, a multisig contract is a frequently deployed contract. However, today each time such …
-
Now, we can firefox logins to a csv file, afaik, can we add the encryption support may be a cryptohash?
-
The code in `url_CryptoHash_get_general` at URL.cc decodes percent encoding in all components of the URL, including username / password. This behaviour is incorrect and can lead to security consequenc…
-
type ReceiptView struct {
PredecessorID types.AccountID `json:"predecessor_id"`
ReceiverID types.AccountID `json:"receiver_id"`
ReceiptID hash.CryptoHash `json:"receipt_id"`
Receipt …