This category seems to make up a large but distinct portion of the questions here. So far I have seen:

Example question: How do I program BTC Relay into my dapp?

Personally, I'm in favor of standardizing as the de-facto tag for the whole category.

  • Is your question answered?
    – q9f
    Apr 11, 2016 at 8:11

4 Answers 4


I suggest:


I generally agree with your suggestion, buy we may continue to get a variety of those tags. Thanks for using my example - lol.

  • In that case, you can make some synonyms of the tags that often get used instead of the canonical tag. Say smartcontract is a simple example of a dapps, you map smartcontract as a synonym of dapps. Then when someone tries to apply smartcontract it is changed to dapps automatically.
    – Murch
    Jan 24, 2016 at 8:45

The use of and seems to be more appropriate for the development of a smart contract. And I make a suggestion: We can use also to refer the debug, so in that way we delete the tag currently working in the site.


I think this is a distinct category of things that we will probably keep running into. In my industry we call the peocess of making third-party widgets talk to each "Integration" so when there is a clear purpose in someone's question where they take a component like BTCRelay, or Maker's DAI stablecoin, I would think a tag like "Contract-Integration" would fit quite nicely.

Integration I feel is distinct from debugging, because there may be nothing wrong yet tbat needs fixing. You just might need some documentation explained more clealry for you to proceed. I also expect the most common pieces of infrastructure (Coin API, NameReg, etc.) to end up with canonical answers for how to integrate them with you custom contract.

So, specifically for a question like the example linked, I would suggest the tag "Contract-Integration".

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .