Skip to content

Commit

Permalink
README: some line formatting for better display
Browse files Browse the repository at this point in the history
  • Loading branch information
karalabe committed Jul 9, 2024
1 parent 548f11b commit 8372bb1
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ go get github.com/karalabe/ssz

### Static types

Some data types in Ethereum will only contain a handful of statically sized fields. One such example would be a `Withdrawal` as seen below.
Some types in Ethereum will only contain a handful of statically sized fields. One example is a `Withdrawal`:

```go
type Address [20]byte
Expand All @@ -67,7 +67,7 @@ type Withdrawal struct {
}
```

In order to encode/decode such a (standalone) object via SSZ, it needs to implement the `ssz.StaticObject` interface:
To encode/decode such an object via SSZ, it needs to implement the `ssz.StaticObject` interface:

```go
type StaticObject interface {
Expand Down Expand Up @@ -139,7 +139,7 @@ type ExecutionPayload struct {

Do note, we've reused the previously defined `Address` and `Withdrawal` types. You'll need those too to make this part of the code work. The `uint256.Int` type is from the `github.com/holiman/uint256` package.

In order to encode/decode such a (standalone) object via SSZ, it needs to implement the `ssz.DynamicObject` interface:
To encode/decode such an object via SSZ, it needs to implement the `ssz.DynamicObject` interface:

```go
type DynamicObject interface {
Expand Down

0 comments on commit 8372bb1

Please sign in to comment.