-
In order for the
- https://github.com/aeternity/aesophia/issues/197
- https://github.com/aeternity/aesophia/issues/295
combo to be able to clone existing onchain contracts we need to keep the by…
-
In Review Standard proposal:
https://github.com/aeternity/AEXs/issues/141
First plan support, how do we do the integration, what endpoints will be needed? First use-case would be the explorer I'd …
-
I updated the new version of the SDK and found that the 8.2.0 call contract failure problem was resolved, but when I set the compiler address myself, I found that the request and the set address were …
sunbx updated
2 years ago
-
The compiler doesn't complain if you put a contract function interface somewhere into the contract, like https://studio.aepps.com?highlight=19-5-17-1&contract=036202a2-5 (corresponding tab doesn't foc…
-
In case of error, `/compile` endpoint responses:
```json
[{
"message":"Unbound variable baz at line 3, column 32\\n",
"pos":{ "col":32, "line":3 },
"type":"type_error"
}, {
"message":…
-
https://mainnet.aeternity.io/mdw/swagger/swagger.json
shouldn't it be `["https"]` instead of `["http"]`?
-
aeproject tells me the env is not running. but nginx and compiler are still running. I think we should cover all containers with this command
```sh
marc0olo@DESKTOP-B1QLEDL:~/git/aeternity/aepp-so…
-
Compiling of the contract:
```
@compiler >= 6
include "BLS12_381.aes"
namespace BLS12_381 =
type fp = int
main contract Bug =
type number = int
```
leads to the following er…
-
I wonder what's the reason to include newline in the compiler error output? This is a bit harsh to parse by other tools and would be even more ambiguous if multiple error messages are printed.
-
```
$ make docker
Using default tag: latest
latest: Pulling from aeternity/builder
68e7bb398b9f: Pull complete
2118477f797b: Pull complete
a788903329d3: Pull complete
57b7b5d23a9e: Pull comp…