-
I think we're just using the `horizon` value as-is during fast-sync and not using it relative to the the head. So it is treated effectively as a hard-coded height.
https://github.com/mimblewimble/g…
-
Right now we fast sync by -
* requesting all block headers
* requesting a txhashset
* requesting full blocks after horizon
The third step requires us to request full blocks from peers.
We…
-
Looking into this more now, previously when full sync was the only options, all blocks were contained within the database making it easy to retrieve outputs by height. However, after fast-sync, the fu…
-
This functionality was commented out and disabled as part of #753.
We _are_ compacting the hash file but the data file is left un-compacted.
Now that #753 is merged in we should investigate and get …
-
The block height of coinbase output seems to be wrong after the command
`grin wallet -p password outputs
`
You can see it on this first screenshot : [(https://imgur.com/a/VLH34)](https://imgur…
-
Right now when the wallet restore finds a potential match for an output, it scans through a certain number of key possibilities until it finds the correct blinding factor. This means it's possible to …
-
```
Mar 13 16:01:30.642 ERRO Failed to get coinbase from http://127.0.0.1:13415/v1/receive/coinbase. Run grin wallet listen
Mar 13 16:01:30.643 ERRO Successfully received coinbase from http://127.0.…
-
I believe that #1020 completely destroys Grin's security properties and should be reverted. Although the kernel offset was always just turned into a commitment, the fact that it was stored and transmi…
-
~~Looks like new nodes are unable to connect to old nodes (before https://github.com/mimblewimble/grin/commit/bd64c6099f7f1798d54c3b7cef8f5acbddf6c2e7).~~
On restart, looks like node are tagging old …
-
For example -
https://grinexplorer.net/block/5df58803ba2df2eb3f649bd1cae11e93ffb8f649b075169fd0709764a4a2046c
Block reward is 50 grin
Fees should be considerably less than that (milligrins?)
…