Thoralf-M

Results 15 issues of Thoralf-M

## Description If there are pending protocol parameters, they should be added in the nodeinfo here https://github.com/iotaledger/bee/blob/bd71aa0972b2b6bcf25a8eee06ab9696df98c120/bee-api/bee-rest-api/src/endpoints/routes/api/core/v2/info.rs#L78 ## Motivation So clients can get the data ## Are you planning to...

wg-api
n-shimmer

## Bug description Currently one can build an output with a higher amount in the storage deposit return unlock condition than the actual amount of the output has ``` Basic(BasicOutput...

c-bug
n-shimmer
wg-block

## Description Add methods to check if an output can be unlocked at a provided unix timestamp + milestone index combination ## Motivation With the expiration and timelock unlock conditions...

c-feature
n-shimmer
wg-block

## Description Update parent block ids with new tips during local PoW if it takes more than ~5 seconds. ## Motivation So the final block will always reference new tips...

T - Enhancement

## Description Add a HexString type for strings that are hex encoded ## Motivation Makes it clearer to work with ## Requirements 1. Fields that are currently a `string`, but...

T - Enhancement

https://github.com/iotaledger/crypto.rs/blob/752321d556ab7f391d7f3afb98b71adeef6d23b3/src/keys/bip39.rs#L16 accepts any `str` and https://github.com/iotaledger/crypto.rs/blob/752321d556ab7f391d7f3afb98b71adeef6d23b3/src/keys/bip39.rs#L195 also accepts mnemonics with a space added. Should the verify function return an error if there is a space added or should the mnemonic_to_seed...

## Description Chronicle returns a wrong ledgerInclusionState for a message id https://chrysalis-chronicle.iota.org/api/mainnet/transactions/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be ``` {"data":{"messageId":"12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be","milestoneIndex":6980566,"outputs":[{"output":{"type":0,"address":{"type":0,"address":"eb8bc8b275fbc66500255f06de458ec5b6623b4171b17d8a26a47604860b3885"},"amount":19999500000},"spendingMessageId":null}],"inputs":[{"type":0,"transactionId":"9cc394d188acec61fd76b1ca13554390b02ab00170cad1bc7a6e28a8ede09409","transactionOutputIndex":2}],"ledgerInclusionState":"conflicting"}} ``` `conflicting`, but the message with the transaction payload actually got `included` as seen here https://chrysalis-nodes.iota.org/api/v1/messages/12e275f02a4316a83d2ee4c896c18f43f182548a5598a7038a01788244bf88be/metadata...

When I use the command, it can take minutes to get an response, even if the transactions aren't very old. Maybe we can use "local milestones" to optimize that as...

enhancement
help wanted

Add link to https://github.com/iotaledger/documentation