Roger Hernandez

every endpoint that accepts `account` works like this... with the updates we are making now we will be removing this because it has some issues: - extra call as mentioned...

Hello, I think you are forgetting the tail of the expression to get the Constraint object out of it (**.constraint**), such as: ```var destinationAddressViewBottom: Constraint? = nil destinationAddressViewBottom = make.bottom...

> Posting this related issue there > > if A has not announced its public key to the network > B adds A as a cosigner of C > A's...

ok, just wanted to make sure issues were not being duplicated i suppose you mean the `/transactions/partial` endpoint` ^^ @martinayora will take a look at this and give you a...

to clarify: there are two issues within this one, we will try to take a look "soon"

i agree with this, however i do not think it is a bug, and it is working as expected, the documentation is very clear on it in here https://nemtech.github.io/symbol-openapi/v0.8.10/#operation/getTransactionFees >...

> In this case, the API could either return undefined or calculate the feeMultiplier with the number of blocks available < numBlocksTransactionFeeStats i'd not be happy with adding a default/fallback...

this is an internal change that should not have outside effects (API), we will keep delivering longs in HEX/string format, we are just taking this chance now that we updated...

this will probably require a schema file of allowed fields and which type do they have, creating another dependency towards core - but at the same time it will serve...

this issue is a bit controversial because for it to feel "complete" it'd require heavy parsing - we can remove the quotes that enhance readability from the large numbers (define...