oasis-sdk icon indicating copy to clipboard operation
oasis-sdk copied to clipboard

Official SDK for the Oasis Network.

Results 129 oasis-sdk issues
Sort by recently updated
recently updated
newest added

Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 3.2.0 to 3.3.1. Release notes Sourced from golangci/golangci-lint-action's releases. v3.3.1 What's Changed build(deps-dev): bump @​typescript-eslint/parser from 5.40.0 to 5.40.1 by @​dependabot in golangci/golangci-lint-action#590 build(deps-dev): bump eslint from...

c:testing
c:deps

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.4 to 1.8.1. Commits b747d7c Bump github.com/stretchr/objx from 0.4.0 to 0.5.0 (#1283) 181cea6 impr: CallerInfo should print full paths to the terminal (#1201) cf1284f Allow mock expectations...

c:client-sdk/go
c:deps

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 3.1.1 to 3.2.0. Release notes Sourced from docker/build-push-action's releases. v3.2.0 What's Changed Remove workaround for setOutput by @​crazy-max (#704) Docs: fix Git context link and add more...

c:testing
c:deps

Bumps [github.com/btcsuite/btcd](https://github.com/btcsuite/btcd) from 0.22.0-beta to 0.22.1. Changelog Sourced from github.com/btcsuite/btcd's changelog. ============================================================================ User visible changes for btcd A full-node bitcoin implementation written in Go Changes in 0.22.1 (Wed Apr 27...

c:testing
c:deps

Based on #1118 TODO * [x] Use base inmsg gas cost from core parameters. * [ ] Add more tests.

One could do the following stupidity, which is not very obvious ``` oasis accounts deposit 10 paratime:emerald ``` because `to` is an optional argument to deposit cmd and `paratime:emerald` is...

c:cli

Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.47.0 to 1.50.0. Release notes Sourced from google.golang.org/grpc's releases. Release 1.50.0 Behavior Changes client: use proper "@" semantics for connecting to abstract unix sockets. (#5678) This is...

Open questions: * should clients provide additional pers strings? it might be more secure if used properly, but will people know (how) to use it? TODOs: - [ ] tests