Breaking changes

This is a major release. Update your import path to github.com/qubic/go-qubic/v2.

Wire-format change: 4096 transactions per tick

• MaxNumberOfTransactionsPerTick raised from 1024 → 4096. All fixed-size buffers sized by this constant grow accordingly (TickData.TransactionDigests, TransactionStatus.MoneyFlew, TickTransactionEventIDs.FromEventID / Length, request-side TransactionFlags).
• Two stray hardcoded [1024] array sizings now use the named constant.
• TickData.ContractFees stays at 1024 and is now sized by the new MaxNumberOfContracts constant (it indexes by contract ID, not transaction slot).

Module path

• Module path is now github.com/qubic/go-qubic/v2. All consumers must update their imports.
• Proto go_package updated to github.com/qubic/go-qubic/v2/proto/v1;qubicpb (also fixes a prior inconsistency where the directive didn't match the actual Go import path). All .pb.go / .pb.gw.go / _grpc.pb.go files regenerated.

Dependency cleanup

• Replaced github.com/pkg/errors with the stdlib: errors.Wrap / Wrapf → fmt.Errorf("...: %w", ...), errors.Errorf → fmt.Errorf, errors.New / errors.Is resolved from stdlib errors. pkg/errors removed from go.mod.

Upgrade

go get github.com/qubic/go-qubic/v2@v2.0.0

Then rewrite imports: github.com/qubic/go-qubic/... → github.com/qubic/go-qubic/v2/....

See #17.

Full Changelog: v0.3.4...v0.3.5

Add ContractReseveDeduction and OracleQueryStatusChange events.
Increase number of MaxNumberOfSpecialEventsPerTick.

Full Changelog: v0.3.3...v0.3.4

Adds a check for the tick number in event headers and errors, if it does not match the expected tick number (#15).

What's Changed

• 11 qubic client adding ability to run multiple core requests using one connection by @0xluk in #13
• Asset ownership and possession event changes. by @LINCKODE in #14

Full Changelog: v0.3.1...v0.3.2

What's Changed

• Asset issuance event change epoch 183 by @LINCKODE in #12

New Contributors

• @LINCKODE made their first contribution in #12

Full Changelog: v0.3.0...v0.3.1

• The events clients now accepts a list of passcodes for a node ip/hostname as map[string][4]uint. This will be then used to inject the passcode in any request that requires a passcode by looking into which node is being used from the pool and if a password exists for that node.