xdc-community / xips.github.io Goto Github PK

Judging Criteria

XIP stands for XDC Network Improvement Proposal. An XIP is a design document providing information to the XDC community, or describing a new feature for XDC or its processes or environment. The XIP should provide a concise technical specification of the feature and a rationale for the feature. The XIP author is responsible for building consensus within the community and documenting dissenting opinions.

In order to be considered for this bounty you will need to come up with an idea for an XIP, champion it within the XDC Community via xdc.dev and the XDC Community Discord server. Parties involved in the process are you, the champion or XIP author, the XIP editors, and the XDC Core Developers.

Once the idea has been vetted, your next responsibility will be to present (by means of an XIP) the idea to the reviewers and all interested parties, invite editors, developers, and the community to give feedback on the aforementioned channels. You should try and gauge whether the interest in your XIP is commensurate with both the work involved in implementing it and how many parties will have to conform to it. For example, the work required for implementing a Core XIP will be much greater than for an XRC and the XIP will need sufficient interest from the XDC Network client teams. Negative community feedback will be taken into consideration and may prevent your XIP from moving past the Draft stage.

For a complete overview of the XIP process please review XIP-1.

The bounty submission will be considered complete once your XIP is promoted to a status of either "Living" or "Final" depending on the type of XIP. Implementation of the XIP is outside the scope of this bounty, unless the XIP type is Meta.

All submissions will be put through an industry standard plagiarism detection tool to ensure that all submissions are the work and ideas of the person submitting for the bounty. If the plagiarism tools flags your submission you will be disqualified from participation in the bounty.

You will be provided with resources (if available) as an aid to help you get started. The sole act of submitting content for the bounty does not automatically qualify you for the bounty. Our team will review all submissions and will choose the submission whose content best fits the needs and requirements of the bounty.

Multiple participants may be selected as winners for the bounty, and they will be notified within 7 working days after the bounty has ended.

Description

Amount of Bounty

Grant Sponsor: XDC Foundation. All monies paid will be in XDC.

What will you be creating?

You will be creating an XIP for the XDC Network, championing an improvement from inception of the idea through acceptance of the XIP by the XDC Developer Community.

Details

Champion an XIP from inception to acceptance

Champion an XIP from idea inception to acceptance by the XDC Developer Community

What you will do

• Identify an improvement to the XDC Network
• Champion the improvement on XDC.dev or the XDC Community Discord server.
• Write the XIP
• Shephard the XIP through the XIP Workflow until it reaches a state of "Living" or "Final"

Total Prize of Bounty

Total sum of up to $3,000.00 USD worth of XDC for this event per accepted XIP, reward amount assigned at judge's discretion.

Further Details

All XIPs will be open source under CC0 and added to the XIPs repository pull request:

XIP Repository

Resources

These are some of the resources you have available to you where you will find the necessary information to complete your submission.

XIP-1

https://xips.xdc.community/XIPS/xip-1#what-is-an-xip

XDC Dev Portal

https://www.xdc.community/pages/xips/

xdc.dev

https://www.xdc.dev/

EIPs

https://github.com/ethereum/EIPs

XDC chain does not support eip-1186 (eth_getProof) now. Some software use this feature such as helios.

XinFin blockchain does not support EIP-1898 now. Below methods are are affected:

• eth_getBalance
• eth_getStorageAt
• eth_getTransactionCount
• eth_getCode
• eth_call
• eth_getProof

Here is a test case：

request

curl -X POST https://arpc.apothem.network/ -H "Content-Type: application/json" -d '
{
    "id": 348,
    "jsonrpc": "2.0",
    "method": "eth_call",
    "params": [
        {
            "data": "0x06fdde03",
            "gas": "0x2faf080",
            "to": "0x53350795c11cee781a7e174479778f848d76ab2a"
        },
        {
            "blockHash": "0xe8ec0bfc021f839fd0a69ae89689e309632af2cc434e8a096732068f0736864b"
        }
    ]
}'

response

{
  "jsonrpc": "2.0",
  "id": 348,
  "error": {
    "code": -32602,
    "message": "invalid argument 1: hex string without 0x prefix"
  }
}