eth 0.5.8 → 0.5.10

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8bb2370cb186c41e849c2949bbfcc1cb5cc6b2572064d8abba4631ed3ed3a692
-  data.tar.gz: dabde7655f7d8921f05a1cdb5d860981c3ee4cced8e1a7b085482d01b14c24b1
+  metadata.gz: 1fd0b420dd7b4641fe8e87f57f13fdb74b3a23a2c11e7c2e23355f1cc5f6b4a3
+  data.tar.gz: e0c219b1c827ec4fcd4d730bfbb7d7e819a9d3049df6f01271cb79d7a81191ea
 SHA512:
-  metadata.gz: 23a6ac9854368723b40fc0e46fed5e7ae90d1691358538f94cf8a9a43c333dc3e002e5d359513914440823501f882608d9e55e7a71a5a19ee88d38a57498a570
-  data.tar.gz: 14f5f74ea076a2fbdd5b538521a2b4006e58bf9105e34f0a942560841371f69a48cf80e86c680228ee5253e9483c3d85a857aeea7f48e8f4c1698a0f5ae0236c
+  metadata.gz: cdfa9a6cc91db7fba7e6ffe02dba0c4ec5a3e93a4948c5080f461f20415a9803b566dbf8049a63951e82c85007b31202d1826bc2261fc0e6d806bc4af0caade9
+  data.tar.gz: 97d962828b3c98387127ba69505a1170ef43ac8a40ba8aa70dc017cdc9ed91ca790b331fca7ca22eea3ba4d25158fcf3fb9e214bd195472a5b27b4bbc22ad790

data/.github/workflows/spec.yml

@@ -35,7 +35,7 @@ jobs:
       run: |
         sudo add-apt-repository -y ppa:ethereum/ethereum
         sudo apt-get update
-        sudo apt-get install ethereum solc
+        sudo apt-get install ethereum solc libyaml-dev
       if: startsWith(matrix.os, 'Ubuntu')
     - name: Run Geth
       run: |
@@ -50,3 +50,4 @@ jobs:
         bundle exec rspec
       env:
         COVERAGE: true
+        INFURA_TOKEN: ${{ secrets.INFURA_TOKEN }}

data/CHANGELOG.md

@@ -1,6 +1,38 @@
 # Change Log
 All notable changes to this project will be documented in this file.
 
+## [0.5.9]
+### Added
+* Eth/abi: dynamic struct encoding (#135) [#185](https://github.com/q9f/eth.rb/pull/185)
+* Eth/client: support camel case (convert before sending the tx) [#172](https://github.com/q9f/eth.rb/pull/172)
+* Eth/client: add `tx_succeeded?` [#173](https://github.com/q9f/eth.rb/pull/173)
+
+### Changed
+* Eth/client: raise an error if a contract interaction reverts [#186](https://github.com/q9f/eth.rb/pull/186)
+* Eth/client: dup params to prevent marshalling on client obj [#184](https://github.com/q9f/eth.rb/pull/184)
+* Eth/client: add test for tx_succeeded? [#183](https://github.com/q9f/eth.rb/pull/183)
+* Eth: rename functions prefixed with is_ [#182](https://github.com/q9f/eth.rb/pull/182)
+* Eth/chain: update available chains [#181](https://github.com/q9f/eth.rb/pull/181)
+* Docs: update changelog for 0.5.8 [#180](https://github.com/q9f/eth.rb/pull/180)
+* Eth: happy new 2023 [#179](https://github.com/q9f/eth.rb/pull/179)
+* Docs: fix readme workflow badge [#178](https://github.com/q9f/eth.rb/pull/178)
+* Solidity: sanitize the contract path before compiling [#176](https://github.com/q9f/eth.rb/pull/176)
+* Ci: add libyaml on ubuntu [#175](https://github.com/q9f/eth.rb/pull/175)
+
+## [0.5.8]
+### Added
+* Client: ability to manual set nonce of tx for transfer, deploy, transact methods was added. [#169](https://github.com/q9f/eth.rb/pull/169)
+* Client: ability for call contract methods with specific transaction value was added [#168](https://github.com/q9f/eth.rb/pull/168)
+* Client: add ENS resolve support [#150](https://github.com/q9f/eth.rb/pull/150)
+
+### Changed
+* Client: satisfy yard docs for transfer kwargs [#170](https://github.com/q9f/eth.rb/pull/170)
+* Client: remove invalid parameters from call_raw method [#166](https://github.com/q9f/eth.rb/pull/166)
+* Gem: bump required ruby version to 3 [#165](https://github.com/q9f/eth.rb/pull/165)
+* Build(deps): bump JamesIves/github-pages-deploy-action from 4.4.0 to 4.4.1 [#162](https://github.com/q9f/eth.rb/pull/162)
+* Gem: bump version to 0.5.8 [#161](https://github.com/q9f/eth.rb/pull/161)
+* Docs: update changelog [#160](https://github.com/q9f/eth.rb/pull/160)
+
 ## [0.5.7]
 ### Added
 * Eth/client: add http basic support auth ([#151](https://github.com/q9f/eth.rb/pull/151))

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,122 @@
+
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+<github@q9f.cc>.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

data/CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing to Ruby Ethereum
+
+Everyone is welcome to contribute to the Ruby Ethereum gem. It is
+more than six years old and had seen many maintainers come and go.
+
+Current maintainers:
+* [@q9f](https://github.com/q9f)
+* [@kurotaky](https://github.com/kurotaky)
+
+### Workflow
+
+To propose a change, fix, or new feature, create an issue or comment
+on an existing issue to see if anyone else has an opinion on it or is
+eventually already working on it
+
+The general workflow looks roughly like this:
+
+1. Discuss it
+2. Fork it
+3. Improve it
+4. Test it
+5. Document it
+6. Submit it
+
+### Linting
+
+We use the Ruby formatter `rufo` to ensure consistent formatting across
+the code base.
+* <https://github.com/ruby-formatter/rufo>
+
+Simply run `rufo .` before comitting your changes.
+
+### Testing
+
+We use behaviour-driven development and this codebase is at least 100%
+unit tested. We use RSpec to run the spec tests.
+* <https://rspec.info>
+
+The full Ethereum test-suite is available in `fixtures/ethereum/tests`.
+Run `git submodule update --init --recursive` to fetch it.
+* <https://github.com/ethereum/tests>
+
+If your tests are failing make sure you pulled the ethereum/tests 
+submodule and run a local geth node in background with
+`geth --dev --http --ipcpath /tmp/geth.ipc` as we are running some tests
+against a local live node.
+
+Other static test data is available in `fixtures/`
+
+### Documentation
+
+We use the Ruby documentation tool Yard.
+* <https://yardoc.org>
+
+The code base is 100% API documented.
+* <https://q9f.github.io/eth.rb>
+
+More involved documentation, tutorials, and usage examples should go
+into the wiki.
+* <https://github.com/q9f/eth.rb/wiki>
+

data/LICENSE.txt

@@ -187,7 +187,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright (c) 2016-2022 The Ruby-Eth Contributors
+   Copyright (c) 2016-2023 The Ruby-Eth Contributors
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

data/README.md

@@ -6,7 +6,7 @@
 
 # Ethereum for Ruby
 
-[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/q9f/eth.rb/Spec)](https://github.com/q9f/eth.rb/actions)
+[![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/q9f/eth.rb/spec.yml?branch=main)](https://github.com/q9f/eth.rb/actions)
 [![GitHub release (latest by date)](https://img.shields.io/github/v/release/q9f/eth.rb)](https://github.com/q9f/eth.rb/releases)
 [![Gem](https://img.shields.io/gem/v/eth)](https://rubygems.org/gems/eth)
 [![Gem](https://img.shields.io/gem/dt/eth)](https://rubygems.org/gems/eth)
@@ -23,7 +23,9 @@ A straightforward library to build, sign, and broadcast Ethereum transactions. I
 
 What you get:
 - [x] Secp256k1 Key-Pairs and Encrypted Ethereum Key-Stores (JSON)
+- [x] EIP-20 Token Transfers (ERC20)
 - [x] EIP-55 Checksummed Ethereum Addresses
+- [x] EIP-137 Ethereum Domain Name Service (ENS)
 - [x] EIP-155 Replay protection with Chain IDs (with presets)
 - [x] EIP-191 Ethereum Signed Messages (with prefix and type)
 - [x] EIP-712 Ethereum Signed Type Data
@@ -36,7 +38,7 @@ What you get:
 - [x] RLP-Encoder and Decoder (including sedes)
 - [x] RPC-Client (IPC/HTTP) for Execution-Layer APIs
 - [x] Solidity bindings (compile contracts from Ruby)
-- [x] ~~Full~~ Some smart-contract support (deploy, transact, and call)
+- [x] Full smart-contract support (deploy, transact, and call)
 
 ## Installation
 Add this line to your application's Gemfile:
@@ -78,6 +80,8 @@ The test suite expects working local HTTP and IPC endpoints with a prefunded dev
 geth --dev --http --ipcpath /tmp/geth.ipc &
 ```
 
+It also expects an `$INFURA_TOKEN` in environment to test some ENS queries on mainnet.
+
 To run tests, simply use `rspec`. Note, that the Ethereum test fixtures are also required.
 
 ```shell

data/SECURITY.md

@@ -0,0 +1,24 @@
+# Security Policy
+
+## Supported Versions
+
+Ruby Ethereum 0.5.0 is a complete rewrite of the old `eth` 0.4.x gem.
+It also contains modules from `abi`, `rlp` and the `ethereum` gem.
+
+None of these gems are maintained anymore except for `eth` 0.5.0 and
+later.
+
+| Gem            | Version | Supported          |
+| -------------- | ------- | ------------------ |
+| `eth`          | 0.5.x   | :white_check_mark: |
+| `eth`          | < 0.5   | :x:                |
+| `ethereum`     | _any_   | :x:                |
+| `ethereum-abi` | _any_   | :x:                |
+| `rlp`          | _any_   | :x:                |
+
+## Reporting a Vulnerability
+
+Please report your findings to <security@q9f.cc>. Do not create a
+Github issue!
+
+You can expect an answer within 48 hours.