IDEA: Position Badges Concept – An automated job posting and personal on-chain resume

General
1

In the discussion on automating job postings, it was suggested that badges corresponding to each role could be issued when someone assumes a position, with the front end displaying the announcement based on on-chain data. This could be a solution that balances multiple aspects.

  • It would further advance full on-chain governance.
  • Other collaborating organizations could integrate on-chain data as well.
  • Individuals’ historical credentials would be clear at a glance, and a feature similar to a personal profile could be introduced to display a person’s on-chain credentials.
  • If it could be promoted across multiple organizations, with data formats standardized, it might even be possible to launch a public platform for issuing badges.

Further considerations:

  • If combined with a voting system, could badges be issued after voting? For example, could the function of issuing badges be authorized to a voting contract?

Current conditions envisioned for these badges:

  • Non-transferable
  • An expiration period needs to be set upon issuance
  • Clearly corresponds to the organization and the position
  • Data about both the individual and the position should be iterable

在岗位公示自动化的议题上讨论到如果每个岗位上任时，发放岗位对应的badges，前端根据链上数据呈现公示，可以是一个兼顾多方面的解决方案。

  • 对于全链上治理又更进一步
  • 其他合作组织也可以透过链上数据整合
  • 人员的历史资历一目了然，可以推出一个类似个人名片的功能，显示这个人的链上资历
  • 如果可以推广到多个组织，让数据格式统一化，甚至可以推出一个公用的发放平台

进一步思考：

  • 如果结合投票系统，能不能通过投票后系统发放？例如将发放的功能授权给投票合约？

目前想到这个badges具备的条件

  • 不可转移
  • 发放时需要设定有效期间
  • 明确对应的组织跟岗位
  • 人跟岗位的数据都可被历遍
4 Likes
2

一开始的话，我觉得 badges 是不是就单纯作为某种声誉徽章比较合适
组织、岗位这些可以根据官网公示
这样可以先执行一部分起来，不需要一开始就设计得特别复杂

3

但是这几点在合约里都不是太难写啊

4

I think this is a necessary feature for DAO OS. I was thinking to implement it on Database, but seems better to use on-chain credential.

But, we do need to think about the smart contract design, might not be that easy.

It should be SBT, but can be controlled by the DAO and orgs. Previously, we design LXDAO BuidlerCard by following employee card, set status like Active, Archive, etc. based on their status. But I think it is good to destroy the SBT to indicate they have left the position.

We also need to think about the centralization issue, for example, who can control the SBT issuance and why. If we want to make it on-chain resume, we do need to convince people to believe it is reliable.

1 Like