bnb-chain/beps

BNB Evolution Proposals

beps's Issues

Bumps [phoenix_html](https://github.com/phoenixframework/phoenix_html) from 3.0.4 to 3.3.2.

Bumps phoenix_html from 3.0.4 to 3.3.2.

Changelog

Sourced from phoenix_html's changelog.

v3.3.2 (2023-08-10)

• Enhancements

  • Address deprecations in Elixir v1.16+

• Deprecations

  • Deprecate inputs_for/2 and inputs_for/3 (without anonymous functions)

v3.3.1 (2023-02-27)

• Bug fix
  • Set display to none on generated forms
  • Warn for maps with atom keys

v3.3.0 (2023-02-10)

• Enhancements

  • Support deeply nested class lists
  • Implement Phoenix.HTML.Safe for URI
  • Implement Phoenix.HTML.FormData for Map

• Bug fix

  • Generate unique IDs for checkboxes based on the value
  • Use artificial button click instead of form.submit in JavaScript to trigger all relevant events
  • Fix a bug where nil/false/true attributes in aria/data/phx would emit empty or literal values, such as "true" and "false". This release aligns them with all other attributes so both nil and false emit nothing. true emits the attribute with no value.

• Deprecations

  • Phoenix.HTML.Tag.attributes_escape/1 is deprecated in favor of Phoenix.HTML.attributes_escape/1

v3.2.0 (2021-12-18)

• Enhancements
  • Raise if the id attribute is set to a number. This is actually an invalid value according to the HTML spec and it can lead to problematic client behaviour, especially in LiveView and other client frameworks.
  • Allow phx attributes to be nested, similar to aria and data attributes
  • Allow hidden fields in forms to be a list of values

v3.1.0 (2021-10-23)

• Bug fix
  • Do not submit data-method links if default has been prevented
• Deprecations
  • Deprecate ~E and Phoenix.HTML.Tag.attributes_escape/1
  • Remove deprecated Phoenix.HTML.Link.link/1

Commits

• 0d394e9 Release v3.3.2
• 9464dfb Fix docs and deprecate entries in inputs_for
• ed9a2a1 docs: fix some typos and improve readability (#424)
• 102fa95 Mention phoenix_ecto in FormData protocol docs (#423)
• b668683 Fix typo in sample code (#420)
• cf704e4 Bump CI again
• 813a1fb Bump CI range
• 4810b0a Document form[field] access quirks (#419)
• cad7b0d Document the options in the protocol
• 45cd6ad docs: fix argument value (#414)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Originally posted by @dependabot in blockscout/blockscout#8171

The withdrawal address of the wallet

0x20fE9F5896A3021Ca6eA78005a15AE954dC134E6

0x43b9D7c4a8527ED6598A13e655012eC85890CC33

fast bsc token generator

http://www.coinmaker.fun/

Lost my BNB.

I was on binance.org and I cannot find my bnb amount. I am not tech savvy and I think I may started a wallet but do not know which one one. I have my ledger nano X and would appreciate if anyone here can help me retrieve it. I will definitely compensate the person who helps me out. Awaiting someone to guide me. Thanks to anyone who can help.
Hope to hear form you.
Anukshuk

BEP-131 delegator income reduce problem

With the number of validators increased, this means one single validator will validate fewer blocks than before, which means the income of the stakers will get reduced?

How to use binance Smart chain faucet

Please how to use binance Smart chain faucet

Slash rule for candidate validator should be tougher than ordinary ones

According to https://github.com/bnb-chain/BEPs/blob/master/BEP131.md ,

On the other hand, all the slash rules also work on Candidate validators to ensure the malicious or negative behaviors from Candidates will be punished.

Since candidates are less likely to seal new blocks, thus less likely to reach slash threshold.

Assuming an ordinary validator will be jailed after 150 slashed i.e. 2.5 hours -ish downtime, and BEP131 was deployed as MaxNumOfCandidates= 20 and MaxNumOfWorkingCandidates = 2, we will come to the situation that a candidate validator will be jailed after around 2.5*20/2 = 25 hours downtime.

That's almost a whole day, which means a candidate validator will never be slashed because of downtime.

Ameralamero

Go this

Yaya

To address the 1 GWei Gas Price issue

Currently, most of the validators only accept gas price >=5Gwei, but some validator may not follow this rule.
The Gas Price is not part of the consensus yet, may need to dive deep and discuss within the community to see if it is necessary to add it as part of the consensus.

Shotota

Shotota

Originally posted by @sheakhasan926 in #119 (comment)

When BEP-151

When do you plan to do it mainnet?

Are there any alternative solution to EIP-1344 and EIP-155?

We're building a Multi Signature Solution and facing a serious problem about replay attacks. The CHAINID opcode is necessary for on-chain verification of an ECDSA proof and preventing the proof to be used on another chain. I can't see the proposal of chain id opcode in this repo.

Where could I check the compatible and incompatible between BNB Chain an Ethereum?.

Compare & pull request

Compare & pull request

Originally posted by @Nouri11190 in #283 (comment)

P

Track BEP Idea: To Support StateExpiry

will update the progress of State Expiry in this issue.

• 2022.01.18: Idea first published on https://forum.bnbchain.org/t/bep-idea-state-expiry-on-bnb-chain/646

What is OB and CB ?

What's the full name of OB/CB？

When reading the document, I was confused by the sudden abbreviation

https://github.com/binance-chain/BEPs/blob/master/BEP3.md#client-swap-tokens-from-ethereum-to-binance-chain

To address the ChiToken on BSC, like EIP-3529

BSC does not address the ChiToken yet, may need to solve it.
Ethereum has solved it in London Upgrade, with EIP-3529.
may refer: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-3529.md

https://github.com/binance-chain/BEPs/blob/master/BEP2.md#532-transfer-tokens does not show transfer fee applicable for asset transfer

Trying to find out the actual BNB tansfer fee required for asset token transfers, but this is nowhere stated and also not clear if we need to provide a fee when doing the transaction. Please add this to the documentation.

eth_sendRawTransaction method is succsess but transaction doesn't exist

  {
      "id":1,
      "jsonrpc":"2.0",
      "method":"eth_sendRawTransaction",
      "params": ["0xf8ae84307836668512a05f200082dba494b84cbbf09b3ed388a45cd875ebba41a20365e6e780b844a9059cbb000000000000000000000000c3f069f88af54d17dd025538d532dd72ca9a166600000000000000372c3030302c3030302c3030302c3030302c3030302c3030308194a0830ae458deacbf377c1c205ae736aa70299d2b20f009edeb288f0eb313155d3ba006dcde67ec5d6347acc778f0816449192400255ced945f0437f587be979b5edc"]
  }

i'm trying to send a BitShiba token, I used to get a lot of errors and I could work with it somehow, but now I'm getting

      {
        "jsonrpc": "2.0",
        "id": 1,
        "result": "0xc852c10c4ccc4daa5b9916d49f68f56ff4922b01c0f49cae0af3749684358c1c"
      }

and this confuses me, because it is success but the transaction itself does not exist, and the tokens are not sent, what to do about it?

Fixates the version, marks as release, sets the year of release10/19/ 2023

Fixates the version, marks as release, sets the year of release.

Blocked until we make final decisions on all open PRs under the 1.14.6 milestone.

Originally posted by @jacksonbinh4 dogecoin/dogecoin#3048

When will you start supporting EIP-4337

When will you start supporting EIP-4337 & EIP1559?

MEV on BSC - where we are and where we should go

Recently, several validators began to quietly capture MEV.
This development was predictable, but has some negative effects:

1. Unfairness - it's unfair that some validators make more $ by extracting MEV, while others do not.
   Whatever decision the BSC community reaches regarding MEV - it should be fair for all validators.
2. Centralization - MEV validators yield higher APY, causing stakers to abandon other validators and concentrate the stake with the best MEV-extracting validator.
   Any MEV solution should allow all validators to capture similar yield to avoid it.
3. Half-measure is the worst of all worlds.
   It's fine if validators don't capture MEV, and it's potentially fine if they do.
   But if some of the validators extract MEV while others don't, it's bad for the traders who lose trades, and bad for MEV searchers who can only capture a fraction of the opportunity.
4. No clear standards.
   Right now each actor acts independently without synchronization. Having clear guidance from the BSC community and foundation would allow any solution/approach (no matter what it is) to be utilized effectively across the ecosystem to everyone's benefit.

The problem of centralization is so significant, that on ETH it drove the adoption of MEV-boost, which allows 3rd-party block-builders to suggest blocks which capture MEV.
The rational is something like: if a vanilla solo-validator yields 4% APY, and a large validator can invest in capturing MEV and yield 7% APY, everyone will stake with the 7% MEV validator.

We would like to explore potential MEV solutions to the BSC ecosystem, balancing between:

• Validator yield
• Decentralization
• DeFi user experience

bloXroute will be glad to explore, collaborate, implement, and/or maintain a MEV solution which best fits the BSC community.
Such potential solutions include:

1. MEV-boost-like solution, allowing specialized MEV actors the suggest the most valuable blocks to any validator
2. Implementing Themis - a fair-ordering solution suggested by Cornell / Chainlink - which eliminates MEV and include Tx according to the order they were received by all validators (MEV minimization)
3. Enabling validators to back-run / capture arb, but preventing front-running / sandwiching which is the most harmful for users (only "good MEV")
4. MEV-geth-like solution, allowing Searchers to provide bundles and private Tx to validators, but not full blocks
5. Incentivizing searchers to maintain an open-source code which allows validators to capture MEV locally
6. Back-running MEV auctions which allow validators to back-run, but prevents front-running

or a combination of the above.

This post doesn't offer a solution - rather, it's an invitation to collaborate and explore which MEV approach would serve the BSC ecosystem best and get it done fast.

As a service provider for some of the largest DeFi traders in the world, and as key actor in multiple alternative MEV ecosystems on different chains, we would be glad to do our part and contribute to the BSC ecosystem.

Why there is no refund transaction type in BEP3?

In BEP3 draft, BNB chain will add 2 transaction types to support HTLC.

1. Hash Timer Locked Transfer (HTLT).
2. Claim Hash Timer Locked (CHTL).

But i am confused how to refund the asset while the time is expired?

                                      ---KOFO-Fundation

How can you know what height ( > 0) to set for state_sync_height

Hi,
I am trying to use state_sync from a given height. The issue is it starts from height 0 even if I tried with different state_sync_height values (e.g. 35000000).

From what I have read on BEP18, it says somewhere that the configured height must match some peer's snapshot height, but I don't know how to find out some peers available snapshots heights information.

Can you provide a working example (I am trying on mainnet, I have version 0.6.1) ?

aa

0x59576Fb376F1FEaEdb9c768A724D8C06304538f5

0x59576Fb376F1FEaEdb9c768A724D8C06304538f5

Originally posted by @aasszzx707 in #132 (comment)

bnb1cryzzz69qtz4g5k4ad6svpsxskt9k4esksk0e5

bnb1cryzzz69qtz4g5k4ad6svpsxskt9k4esksk0e5

BEP3 - Ethereum ERC20 token swap.

As I know some pegged token already launched on Binance. does it mean that BEP3 is already implemented? I was wondering if this is already implemented for Ethereum ERC20 token and I can test it. Please confirm.

BEP 10: Add BrowserBNB Wallet source code

https://github.com/button-tech/BrowserBNB is an open source metamask like wallet that was made during Binance Fellowship program

App is published at Chrome store:
https://chrome.google.com/webstore/detail/bnb-browser/eeflaanifildahldmpahjmgmgippmgne

I want to suggest 2048 as a source code for it

https://github.com/ethereum/ropsten/blob/main/LICENSE#L5

https://github.com/ethereum/ropsten/blob/main/LICENSE#L5

Originally posted by @kaaid in #315

This is a good proposal, which potentially brings significant change in Binance Chain token economy. I suggest we reuse some non-used BEP proposal number, such as 8, instead of 69.

This is a good proposal, which potentially brings significant change in Binance Chain token economy. I suggest we reuse some non-used BEP proposal number, such as 8, instead of 69.

Originally posted by @darren-liu in #69 (comment)

d

Gg

Ain

> Shotota

Shotota

Originally posted by @sheakhasan926 in #119 (comment)

Originally posted by @pomnt in #122 (comment)

How do I increase the token amount?

I created BEP20 token via remix, now I want to increase this token amount. How can I make 100 thousand tokens 200 thousand?

Eth

https://github.com/ethereum/consensus-specs/blob/v0.10.0/specs/phase0/beacon-chain.md

ParserError in BEB20 code

Can't compile the contract, always showing this error message.

Does anybody encounter same

[email protected]

error

Error: Number can only safely store up to 53 bits

Ɓb

Tronprotocol

tronprotocol/zksnark-java-sdk@413cb31

bc1qw72csrx0rh2hea5q00vs63pkc88klvj6j9laj5

0x20fE9F5896A3021Ca6eA78005a15AE954dC134E6

"https://www.paypal.me/AbdulsalamAAmeen".

- Fix parameter type issue in method `AggregateTradesListAsync`, `KlinesAsync` and `UiKlinesAsync`

• Fix parameter type issue in method AggregateTradesListAsync, KlinesAsync and UiKlinesAsync

Originally posted by @2pd in binance/binance-connector-dotnet#48

Hello

Readme not updated with BEP-129

the readme is missing:

#129

is something else missing?

How to access the API

How can I consume the API??
I would like to retrieve the data of the account addresses (balance/tokens held/amounts) in the NodeJs app.
Can someone point me?

Bina