-
**Task description**
Currently concordium-client does not check that the smart contract parameter fits into max parameter size, which is 1024 bytes which then can lead to a "serialization failed" err…
-
Add a new `/preregistration/account/:account?signature=` (GET) endpoint to get the full `preregistration` document in an `application/json` format.
Validations should be returning using 4xx error a…
-
**Description**
If a transaction filter is applied to the transaction log, then some transactions may be hidden. It is not obvious, as a user, whether a filter has been applied or not. This can only …
orhoj updated
2 years ago
-
To get full logs with the original tool, use `concordium-node-retrieve-logs`, see also [Wiki: Logs](https://github.com/Concordium/Testnet3-Challenges/wiki/Logs).
To get smaller pruned logs, please …
-
The GTU drop that can be requested on newly created accounts for test purposes has been increased temporarily from 100 GTU to 1000 GTU to ensure that transfer fees can be paid during the new transacti…
-
**Description**
Currently user has to reload CCDScan page in-order to upload any new data e.g. new transaction or new token added/removed from an account. This should happen automatically or at max. …
-
**Bug Description**
Whenever the page URL changes, the `inject.js` instantiates `WebAssembly`. This causes the tab to quickly run out of memory and start lagging if the URL changes frequently.
*…
-
Update the documentation to include descriptions of the serialization of transactions that are not already described. I suggest that it is done similarly as in https://github.com/Concordium/concordium…
orhoj updated
2 years ago
-
When running your node on Windows, it might fail to bootstrap. In that case, it will not get any peers and does not catch up to the chain or at least not to the full fin length. You can check both e.g…
-
Add a new `/preregistration/claimbeta/:account?signature=` (PUT) endpoint to enter the beta program.
Validations should be returning using 4xx error and a json document:
```json
{
"error": ""
}
`…