4

The following tags might be too broad or too unspecific.

  • could be anything from contract-design to rpc-security or simply chosing weak passphrases
  • could refer to cold-storage or offline signing of transactions
  • is in my eyxes a total useless tag
  • seems like a meta-tag not really aiming at anything
  • is also very broad and could be anything from data on-chain to wallet data, etc.

Are these tags too broad? How to deal with them? Please discuss.

  • What do you mean by "too broad?" Perhaps you can clarify what problem you are seeing that might be in need of a solution. Tags aren't like questions that have too many answers. They are supposed to organize somewhat large swaths of subject matter so folks can find and follow their general interests. Some of those interests are more specific while others remain somewhat general. But the subject of [security] currently has 51 questions while the others only have 20 between them. Is it that they do not describe the question usefully? I'm not sure what folks are being asked to comment about here. – Robert Cartaino Mar 16 '16 at 14:03
4

I have reviewed how these tags are used in practise to see if they can be broken down logically:

  • could possibly be broken down into , / , , security best practises for node operation, security best practises for client/wallet usage, security best practises for contract design,
  • is in most (but not all) cases used a synonym for (Joris: removed or retagged as )
  • is used in different ways, can possible removed at all. (5chdn: removed)
  • in both cases used to question design choices for the EVM & blockchain itself.
  • is mostly used to discuss storing external data on the blockchain, and costs associated with transaction data: , and would cover this. For some of the usages I haven't found appropriate replacement tags yet; please edit!

You must log in to answer this question.

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