Scrypto Lending Challenge (the “Hackathon”) Official Rules


  • ACKNOWLEDGE THAT YOU ARE ENTERING INTO  A BINDING AGREEMENT  between yourself and the RDX Works Limited, 7 Bell Yard, London, England WC2A 2JR, United Kingdom (RDX)/the Sponsor

  • Acknowledge that you have read and consent to the privacy terms published by RDX from time to time LINK TO RDX PRIVACY NOTICE

  • You agree to comply with the terms and conditions of the hackathon platform  which can be found at including your use of the Hackathon Website.



2. Dates and Timing

  • June 17, 2022 (9:00 am UTC) – July 18, 2022 (11:45 pm UTC) (“Submission Period”).

  • July 19, 2022 (9:00 am UTC) – July 22, 2022 (5:00 pm UTC) (“Judging Period”).

  • Winners Announced: On or around July 26, 2022 (2:00 pm UTC).

3. Eligibility

Those who are eligible to enter the Hackathon (“Eligible Entrants”)

  • Individuals who are over 18  (“Eligible Individuals”);

  • Teams of Eligible Individuals (“Teams”);

  • Organizations (including corporations, not-for-profit corporations and other non-profit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry.

An Eligible Entrant may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis.

If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. 

By entering a Submission on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.

4. The Hackathon IS NOT open to: 

  • Individuals or Organizations who are residents, carry on business or are domiciled in, a country, state, province or territory where the local or international law (including sanctions and trade prohibitions) prohibits participating or receiving prizes in crypto tokens or otherwise

  • Individuals and Organisations who are resident domiciled or carry-on business in the following territories are specifically excluded.

    • Brazil, Quebec, Russia, Crimea, Belarus, Cuba, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control) 

  • Individuals and Organisations who are resident domiciled or carry-on business in those countries that are published by RDX Works Limited at  Restricted Countries for Radix Competitions with Token Prizes:

  • together with;

    • Sudan, Afghanistan, Angola, Azerbaijan, Bahamas, Bosnia Herzegovina, Botswana, Burundi, Cambodia, Cameroon, Chad, Congo, Democratic Republic of Congo, Ghana, Guinea, Guinea-Bissau, Eritrea, Ethiopia, Haiti, Iraq, Laos, Libya, Somalia, Madagascar, Mozambique, Nicaragua, Pakistan, Serbia, South Sudan, Sri Lanka, Tajikistan, Trinidad and Tobago, Tunisia, Turkmenistan, Uganda, Uzbekistan, Vanuatu, Venezuela, Yemen, and Zimbabwe OR to any individual or entity on the UK or Jersey sanctions list or the UK Office of Financial Sanctions Implementation’s list of asset freeze targets.

  • Organisers of the Hackathon; organisations involved with the creation management, organisation design, production, promotion, execution, or distribution of the Hackathon, including the Sponsor and Administrator (“Promotion Entities”).

  • Employees, representatives and agents** of Promotion Entities, and all members of their immediate family or household*

  • Designers and sub-contractors including those involved with the design, production, adjudication, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*

  • Any Judge (defined below), or company or individual that employs a Judge

  • An AFFILIATE of any organization described above

  • Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Sponsor and/or Administrator, a real or apparent conflict of interest 

*The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person that shares the same residence as the individual for at least three (3) months out of the year. 

**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.

***An Affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.

5. How to Enter 

Entrants may enter by visiting (“Hackathon Website”) and following the below steps:

  • Register for the Hackathon on the Hackathon Website by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. 

  • This will enable you to receive important updates and to create your Submission. By registering for the Hackathon, you agree that these terms and conditions are binding upon you.

  • Entrants will obtain access to the required developer tools and complete a Project described below in Project Requirements. Use of the developer tools will be subject to the license agreement related thereto. 

  • Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Hackathon.

  • Entrants can access the required developer tools at

    • Install the Scrypto toolchain and make sure you are on v0.4 (or later) with “scrypto --version”.

    • Fork the challenges repository.

    • Clone the forked repository on your local environment.

    • Start a new scrypto project with “scrypto new-package [name]” inside the lending directory.

    • Commit and push your project folder and create a pull request here.

  • Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website, including the URL to your Pull Request, (each a “Submission”) during the Submission Period and follow the requirements below.

Project Requirements

What to Create: Entrants must create a working decentralized application (dApp) offering lending functionality, built using Scrypto. (each a “Project”). 

Functionality: The Project must be capable of being successfully installed and running consistently on the platform for which it is intended and must function as depicted in the video and/or expressed in the text description.

Platforms: A submitted Project must run on the platform for which it is intended, and which is specified in the Submission Requirements. 

New & Existing Projects: Must be either newly created by the Entrant or, if the Entrant’s Project existed prior to the Hackathon Submission Period, must have been significantly updated after the start of the Hackathon Submission Period.

Third-Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them.

Testing: The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends. 

Submission Requirements. Submissions to the Hackathon must meet the following requirements:

  • Include a Project built with the required developer tools and meets the above Project Requirements.

  • Include a text description that should explain the features and functionality of your Project.

  • Submit your Pull Request URL and completed submission form on Devpost.

  • (Optional) Include a URL to your functional demo application 

  • (Optional) Include a demonstration video of your Project. The video portion of the submission:

    • should be less than three (3) minutes

    • should include footage that shows the Project functioning on the device for which it was built

    • must be uploaded to and made publicly visible on YouTube, Vimeo, Facebook Video, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and

Submissions must;

  • not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material.

  • be the original work of the submitter, be solely owned by the submitter, and not violate the IP rights of any other person or entity.

Multiple Submissions. An Entrant may submit more than one Submission, however, each submission must be unique and substantially different from each of the Entrant’s other Submissions, as determined by the Sponsor and Devpost in their sole discretion.

Language Requirements. All Submission materials must be in English or, if not in English, the Entrant must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted. 

Team Representation. If a team or organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. 

By entering a Submission on the Hackathon Website on behalf of a team or organization you represent and warrant that you are the Representative authorized to act on behalf of your team or organization.

Intellectual Property, submissions must: 

  • be your (or your Team, or Organization’s) original work product;

  • be solely owned by you, your Team, your Organization with no other person or entity having any right or interest in it; and 

  • not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. 

An  Eligible Entrant may

  • contract with a third party for technical assistance to create the Submission provided the Submission components are solely the entrant’s work product and the result of the entrant’s ideas and creativity, and the Entrant owns all rights to them. 

  • may submit a Submission that includes the use of open-source software or hardware, provided the Entrant complies with applicable open-source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open-source product. 

By entering the Hackathon, you represent, warrant, and agree that your Submission meets these requirements.

Financial or Preferential Support: 

A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. 

Such Projects include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Sponsor or Administrator any time prior to the end of Hackathon Submission Period.

The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest.

6. Submission Modifications.

6.1 Draft Submissions: Prior to the end of the Submission Period, you may save draft versions of your submission on Devpost to your portfolio before submitting the submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your submission, but you may continue to update the project in your Devpost portfolio.

6.2 Modifications After the Submission Period. The Sponsor may permit you to modify part of your submission after the Submission Period for the purpose of adding, removing or replacing material that potentially infringes a third-party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified submission must remain substantively the same as the original submission with the only modification being what the Sponsor and Devpost permits. 

7. Judges & Criteria.

7.1 Submissions by Eligible Entrants which accord with these rules will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). 

7.2 Judges may be employees of the sponsor or third parties, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the sponsor. 

  • Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the project reasonably fits the theme and reasonably applies the required APIs/SDKs featured in the Hackathon.

  • Stage Two) All submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”):

Entries will be judged on the following equally weighted criteria, and according to the sole and absolute discretion of the judges:

  • Quality and asset-oriented-ness of your code. Did the developer follow asset-oriented design patterns such as identifying users with badges and letting the user withdraw instead of sending tokens directly to an address?

  • Breadth of functionality. The more the user of the blueprint and component can do, the more points the developer gets.

  • Creativity of the concept. Did the developer implement something that we didn’t think about or found original solutions to attack a specific problem?

  • Quality of the documentation and comments in the code. Did the developer write documentation explaining how the blueprint worked and how to test it? Did they write comments in their code to help people understand it?

  • Usage of the frontend javascript SDK and the transaction manifest to allow us to test your components using a web interface. Did the developer use the transaction manifest and the new Javascript SDK, introduced with Scrypto v0.4, to showcase composability and allow easier testing of the blueprint and component?

The scores from the Judges will determine the potential winners of the applicable prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize.

Tie-Breaking. If two or more submissions are tied, the tied submission with the highest score in the first applicable criterion listed above will be considered the higher scoring submission. 

In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two or more submissions are tied on all applicable criteria, the panel of Judges will vote on the tied submissions.

All determination by the Judges and all awards and prizes are in the absolute discretion of the Judging Panel and shall be final and not subject to review or contest.

8. Intellectual Property Rights.

All submissions remain the intellectual property of the individuals or organizations that developed them. By submitting an entry, entrants agree that the sponsor will have a fully paid, non-exclusive license to use such entry for judging the entry. 

Entrants agree that the sponsor and Devpost shall have the right to promote the submission and use the name, likeness, voice and image of all individuals contributing to a submission, without additional compensation, in any media whatsoever promoting or publicizing the Hackathon and its results, during the Hackathon Period and for three years thereafter.  

Some Submission components may be displayed to the public. Other Submission materials may be viewed by the sponsor, Devpost, and judges for screening and evaluation. 

By submitting an entry or accepting any prize, entrants represent and warrant that 

  • submitted content is not subject to third party intellectual property rights or other proprietary rights, including but not limited to trade secrets, confidentiality copyright, patent publicity rights, unless entrant is the owner of such rights or has written permission from their rightful owner to post the content; and

  • the content submitted does not contain any malicious content including but not limited to viruses, trojan horses, worms, spyware or other disabling devices or harmful or malicious code

9. Prizes.



First Place

$XRD to the equivalent value of $5,500

Blog post announcing the winning submissions

Radix swag for up to 5 teammates

Second Place

$XRD to the equivalent value of $3,000

Blog post announcing the winning submissions

Radix swag for up to 5 teammates

Third Place

$XRD to the equivalent value of $1,500

Blog post announcing the winning submissions

Radix swag for up to 5 teammates

Participation Prize

Radix participation NFTs (after the Babylon release) for all Entrants of eligible Projects.

  • Cryptographic tokens are largely experimental and subject to a high degree of legal technical and market risk, volatility, and illiquidity or may have no value at all.

  • Participants warrant that they have made their own investigations and evaluations of any Cryptographic tokens that may constitute a prize or award. For the purposes of calculating USD equivalence this will be based on the closing market price according to CoinGecko on the Winner Announcement date.

  • Save where specifically stated otherwise, prizes are to be awarded in XRD and there shall be no entitlement to redeem these for their fiat equivalent to receive fiat equivalent. 

Entrants warrant and undertake to inform themselves as to the legal requirements applicable to their participation in the Hackathon in each relevant jurisdiction and must comply with all laws and regulations and pay all taxes relating to the receipt, holding and disposition of cryptographic tokens 

Entrants shall be liable for all taxes duties levies fees and costs applicable to their participation in the Hackathon and which arise from the award,  delivery, possession or dealing by and to the Participant of any Prize or award including without limitation purchase tax income and other tax 

Each Entrant warrants that they are lawfully entitled to receive Cryptographic tokens and as such indemnify and holds safe the Sponsor against and in respect of any taxes, liability, duties, fines, penalties, and costs (including legal costs on a full indemnity basis) arising out of or in connection with the award, delivery or receipt of such Cryptographic tokens.

10. Substitutions & Changes

Prizes are non-transferable by the winner. Sponsor in its sole discretion has the right to make a prize substitution of equivalent or greater value. Sponsor will not award a prize if there are no eligible submissions entered in the Hackathon, or if there are no eligible Entrants or submissions for a specific prize.

11. Identification Requirement


No submission or submitter shall be deemed a winning submission or winner until the winner has provided such evidence and documents as the Sponsor shall require identifying the entrant. Such requirement shall apply before and after prospective winners have been announced.

The final decision to designate a winner shall be made by the Sponsor and/or Administrator.

12. Prize Delivery

Subject to identification pursuant to Clause 11) Prizes will be delivered to the Entrant, 

  • INDIVIDUALS to the Entrant’s Representative, if a Team; or to the Organization, 

  • ORGANISATIONS. It will be the responsibility of the winning Entrant’s Representative to authorise one recipient and to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate. 

A Prize in fiat currency will be sent electronically to the Entrant, Entrant’s Representative, or Organization’s bank account, and other required forms (collectively the “Required Forms”), if applicable. Failure to provide correct information on the Required Forms, or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification or the Entrant, or forfeiture of a Prize. Prizes will be delivered within 60 days of the Sponsor or Devpost’s receipt of the completed Required Forms.


Winners (and in the case of Team or Organization, all participating members) are responsible for 

  • any fees associated with receiving or Possession transmission and use of a prize, including but not limited to, wiring fees or currency exchange fees. 

  • reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). 

  • complying with foreign exchange and banking regulations in their respective jurisdictions and reporting participation and or registering the award and/or receipt of the Prize to relevant government departments/agencies, if necessary. 

The Sponsor, Devpost, and/or Prize provider reserves the right to withhold all or part of the prize amount to comply with the tax laws of any jurisdiction in which the participant resides, is domiciled or carries on business.

Winners may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. 

14. Entry Conditions and Release.

By entering the Hackathon, you (and, if you are entering on behalf of a Team, Organization each participating members) agree(s) to the following:

Your participation in the Hackathon is not confidential nor does your participation create any fiduciary, agency, partnership, co-venture or other relationship.

You will be bound by and comply with these Official Rules and the decisions of the Sponsor, Administrator, and/or the Hackathon Judges which are binding and final.


You release, indemnify, defend and hold harmless the Promotion Entities, and their respective parent, subsidiary, and Affiliates, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against

  • any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, 

  • violation of right of publicity, 

  • infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Entrant’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorised or permitted by these Official Rules. 


Without limiting the foregoing, the Released Parties shall have no liability in connection with: 

  • any incorrect or inaccurate information, whether caused by the Sponsor or Administrator’s error, or by any of the equipment or programming associated with or utilized in the Hackathon; 

  • technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;

  • unauthorized human intervention in any part of the entry process or the Hackathon; 

  • technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or 

  • any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Entrant’s participation in the Hackathon or receipt or use or misuse of any Prize.

The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Entrants. Proof of sending or submitting the aforementioned will not be deemed to be proof of receipt by the Sponsor or Administrator.

If for any reason any Entrant’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Entrant’s sole remedy is to request the opportunity to resubmit its Submission. Such a request must be made promptly after the Entrant knows or should have known there was a problem and will be determined at the sole discretion of the Sponsor.

17. Publicity.

By participating in the Hackathon, Entrant consents to the promotion and display of the Entrant’s Submission, and to the use of personal information about themselves for promotional purposes, by the Sponsor, Administrator, and third parties acting on their behalf. 

Such personal information includes, but is not limited to, your name, likeness, photograph, voice, opinions, comments and hometown and country of residence. It may be used in any existing or newly created media, worldwide without further payment or consideration or right of review, unless prohibited by law. Authorized use includes but is not limited to advertising and promotional purposes. 

18. General Conditions. 

Sponsor and Administrator reserve the right, in their sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control.

Sponsor and Administrator reserve the right in their sole discretion to disqualify any individual or Entrant if it finds to be actually or presenting the appearance of tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Official Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.

Any attempt by any person to undermine the proper conduct of the Hackathon may be a violation of criminal and civil law. Should the Sponsor or Administrator suspect that such an attempt has been made or is threatened, they reserve the right to take appropriate action including but not limited to requiring an Entrant to cooperate with an investigation and referral to criminal and civil law enforcement authorities.

If there is any discrepancy or inconsistency between the terms and conditions of the Official Rules and disclosures or other statements contained in any Hackathon materials, including but not limited to the Hackathon Submission form, Hackathon Website, or advertising, the terms and conditions of the Official Rules shall prevail.

The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Entrant, the Sponsor and Administrator. The Sponsor and Administrator will post the terms and conditions of the amended Official Rules on the Hackathon Website. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting of the amended Official Rules or, if no time is specified, the time of posting. 

The Sponsors shall be entitled in their absolute discretion to determine and resolve any ambiguity in these rules.

The Sponsor or Administrator’s failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. 

Should any provision of these Official Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to an Entrant, such illegality or unenforceability shall leave the remainder of these Official Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid. 

The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the sponsor’s intention in a legal and enforceable manner with respect to the invalid or unenforceable provision.

19. Use of the Sponsor/administrators Trademarks

All intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, tradenames, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans and representations are owned or used under license by the Sponsor and/or Administrator. 

Unauthorized copying or use of any copyrighted material or intellectual property without the express written consent of its owners is strictly prohibited. Any use in a Submission of Sponsor or Administrator’s intellectual property shall be solely to the extent provided for in these Official Rules.

All rights are reserved.

20. Limitations of Liability.

All of those who apply to enter the Hackathon hereby release the Administrator and Sponsor from all liability for any loss or damage relating to or arising from the entrants participation in the Hackathon, including without limitation any liability for misrepresentation (to the fullest extent permitted by law and in respect all direct and indirect losses, loss of opportunity or increased costs.

a) RDX shall not under any circumstances whatever be liable to the other, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, for:

  • any loss of profit, revenue, or anticipated savings; or

  • any loss that is an indirect or secondary consequence of any act or omission of the party in question.

b) RDX’s total liability in respect of all loss or damage arising under or in connection with this Contract, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, including , shall in no circumstances exceed £500.00 in respect of all entries and submissions made by You.

RDX’s liability for any loss or damage arising out of participation in the Hackathon including the publication of any code or revelation of any trade secret or confidential information shall be limited to the return of any submissions and to the deletion of any copies held by RDX.

All rights to claim enhanced, punitive and/or multiple damages by operation of any source or concept of law are expressly excluded.

Each of the above limitations shall be separate and in the event that anyone shall be deemed to be unlawful or unenforceable all others shall remain unaffected and enforceable.

Nothing in these terms excludes liability for matters which cannot be excluded by law.

21. Disputes.

The performance of this Agreement the deemed location for all submissions and for the receipt and delivery of rights title and interest in any tokens, and the property wallets, obligations and all causes of action arising out of the submission and determination and delivery of any prizes  and the use, transmission, sale, exchange, possession, use or misuse of  tokens shall be deemed to occur and be in England. 

The situs of all property, rights, transactions obligations and debts shall be determined in accordance with 21.1 irrespective of the

  • location of any person, wallet, computer or 

  • where any copy of any distributed ledger or where any digital assets or

  • where or in what format works including entries/submissions are stored, or any transaction is commenced initiated or submitted

  • the location of any server, storage medium 

  • where copies of any the current state of any distributed ledger, shard, components or representation of the token are located, irrespective of 

    • temporary or permanent location, residence, citizenship or domicile of entrants 

    • location of any public or private key or security device or where these are controlled. 

    • place where any transaction is commenced or performed or where any receiving or sending wallet is located or from where a transaction is initiated. 

Each PARTY (which shall include successors in title) irrevocably agrees on behalf of itself and its successors in title that this AGREEMENT shall be governed and construed in accordance with laws of ENGLAND AND WALES. 

Any dispute or difference arising out of or in connection with: 

  • this AGREEMENT, including the formation of this AGREEMENT whether in tort or in contract; and

  • any difference or dispute arising from or relating to any claim to a right to possession, use, transfer, ownership, (without limitation) of any tokens,

  • any transaction or exchange conducted using or any XRD or other tokens.

shall be resolved by arbitration in London, England before a single arbitrator in English in accordance with the rules of the London International Court of Arbitration. 

No party may seek or commence proceedings or seek recognition registration or enforcement of any judgment order injunction or award against RDX or against any of its assets, tangible or intangible in any jurisdiction save where such injunction award, judgment or order has been granted by an arbitrator in London in accordance with these terms and conditions. 

Any arbitral award obtained in accordance with this clause 21) shall be final and binding and shall be registrable and enforceable against the relevant party in any jurisdiction in which that party has or maintains any assets or a temporary or permanent basis.

All operation of conflict of laws is excluded.

22. Entrant’s Personal Information.

Information collected from entrants is subject to the Devpost’s Privacy Policy, which is available at and the Sponsor’s privacy notice set out at

For questions, send an email to