cosmos
Here are 296 public repositories matching this topic...
It wouldn't start if genesisPath and GCI is specified.
Node v11.8.0
Lotion 0.4.8
`
lotion({
initialState: {
blockNo: 0,
txCount: 0
},
ports: { abci: 58354, p2p: 58355, rpc: 58356 },
GCI:
'08a5972afaf42e5751cd7f1af542c4e5e259e07dd0d45d31ffba3eaced632549',
genesisPath:
'/Users/admin/.lotion/networks/806f53597c1bfb8fdd9d128aca662a19/config/genesis.json'
})
-
Updated
Apr 6, 2022 - TeX
Most of the logic for the lockup module's validations is in the message server, not the keeper.
However the keeper methods are where it should be, as its API safety that should be guaranteed for everything using the lockup module.
Bug after upgrade
Started to see this after recent upgrade:
t=2020-12-29T19:45:41+0000 lvl=info msg="Starting ChainBridge..."
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x633d16]
goroutine 1 [running]:
math/big.(*Int).Cmp(0x0, 0xc0000a1880, 0x0)
/usr/local/go/src/math/big/int.go:326 +0x26
github.com/Chain
-
Updated
Nov 30, 2021 - Go
-
Updated
Mar 30, 2022 - Go
-
Updated
Apr 1, 2022 - JavaScript
Please add the ability to be able to receive the amount requested. When you go to receive for any crypto wallet, you can optionally enter in how much in that cryptocurrency or in fiat currency (which will be converted to crypto) you want to recieve. By filling in the requested amount it will update the QR code and address text which can be copied with the amount so when someone pastes the amount i
Node should not allow feeless report transaction with an unreasonable gas limit
Hello,
When implementing Beefy protocol, based on Grandpa consensus, there are 3 kinds of verifications in a hierarchical structure.
- The top tier verification is MMR root verification, by collecting sufficient validators' valid signatures.
- Based on a valid MMR root, the 2nd tier is block header verification.
-
Updated
Mar 31, 2022
-
Updated
Feb 24, 2021 - C++
-
Updated
Dec 1, 2021 - JavaScript
-
Updated
Feb 28, 2022 - C#
-
Updated
Jun 24, 2021 - HTML
-
Updated
Apr 6, 2022 - JavaScript
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Mar 10, 2021 - Rust
-
Updated
May 12, 2021 - C#
-
Updated
Mar 25, 2022 - TypeScript
It would be good to have some tests that assure us that we are serializing and deserializing correctly. There are two kinds of tests that I can see being particularly useful:
- property-based tests for each serialized type checking that
serialize; deserializeis the identity - snapshot testing to ensure that serialization formats don't change unintentionally
Roundtrip serialization f
-
Updated
Mar 23, 2022 - C#
-
Updated
Oct 26, 2021 - Python
-
Updated
Jan 25, 2022 - HTML
-
Updated
Mar 21, 2022 - Jupyter Notebook
-
Updated
Apr 6, 2022 - Swift
-
Updated
Apr 3, 2022 - TypeScript
Improve this page
Add a description, image, and links to the cosmos topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the cosmos topic, visit your repo's landing page and select "manage topics."


Description