Yunjong Jeong (ollie)

Results 14 issues of Yunjong Jeong (ollie)

## Proposed changes - Harden fastCallTracer (`internaltx_tracer.go`) - Use `abi.UnpackRevert()` to parse revert output. - Harden callTracer (`call_tracer.js`) - Try-catch `bigInt()` - Harden revertTracer (`revert_tracer.js`) - Try-catch `bigInt()` - Update...

## Proposed changes Merging into a feature branch. - Add parameter storage contract. Flattened GovParam.sol from [klaytn/governance-contracts](https://github.com/klaytn/governance-contracts/blob/param-immediate/contracts/GovParam.sol) - Add field `ChainConfig.Governance.GovernanceContract` (just the field. not yet votable) - Add ContractEngine...

## Proposed changes Add `homi setup` flags to help test with functioning AddressBook. **NOTE: GitHub cannot show diffs of `options.go` because it's very big. For meaningful diffs, see https://github.com/blukat29/klaytn/compare/be56e1bd...blukat29:klaytn:homi-patch-abook-bin.** Background...

do not merge

Implement an on-chain governance that stores governance parameters in a smart contract. ## Step 1. Syntactic sugars Until v1.9.0. Merge into `dev` branch. - [x] Encapsulate `Governance` type behind `Engine`...

## Proposed changes Merging into a feature branch. This PR is mutually exclusive with https://github.com/klaytn/klaytn/pull/1507. - Add new votable item `governance.governancecontract` - Validate the `governance.governancecontract` vote for following conditions (see...

## Proposed changes Merging into a feature branch. This PR is mutually exclusive with #1436. - Add new hardfork block number - Add ChainConfig item `ContractGovCompatibleBlock` - Add homi options`--contract-gov-compatible-blocknumber`...

**Describe the bug** The `governance_getStakingInfo` RPC result sometimes contains `Gini: -1`. Gini coefficients is defined between 0 and 1 and `-1` is an invalid value. Request to "latest" block returns...

## Proposed changes - Add the "Securing nodes" page under the Nodes > Core Cell guides. - It's about general security advice for node operators. Note to maintainers: - I...

KIP-162 describes a priority fee mechanism for Klaytn transaction type 2 (EthereumDynamicFee). Discussions to #161

Klaytn has implemented dynamic base fee mechanism in KIP-71, but did not implement priority fee mechanism. Adopting the priority fee in Klaytn can be described in one or more KIPs.