After finishing the Diamonds mission, the last thing I want to see is a page that just says: points credited, and that's it.
It’s crucial to keep this in @Bedrock . Because Bedrock 2.0 isn’t a product you can just grasp with a single click. Users might mint uniBTC for Diamonds or interact with something related to brBTC, but if after completing the mission there isn’t a follow-up explaining 'which path you just took,' many will only remember they did the task, but won’t truly understand Bedrock.
So, I specifically look at that final step after the task is done. For instance, after completing the uniBTC-related tasks, does the page indicate that this is just an entry asset, and what layer they’re currently on? After completing the brBTC-related tasks, is there guidance for users to check the path explanation for that route? If the task involves a vault, is there a display of the capacity status readily available? If there’s an exit involved, are users shown the redemption steps first? This design doesn’t need to be heavy, but it’s best not to leave users stuck on 'task complete.'
Many events are lively, but after finishing, users often don’t know what features they just used. If Bedrock wants to bring new users in through Diamonds, I believe tasks should turn an interaction into a path awareness. Users don’t have to understand all of Bedrock 2.0 right away, but they should at least know: I just interacted with the uniBTC entry, the brBTC route, the vault status, or part of the exit explanation.
BRClaw could also fit in here. For example, after completing a task, provide users with a natural question: you can ask BRClaw, which layer did that step belong to in the Bedrock route? What other path explanations can you check later? This way, the task becomes more than just a task; it leads users into the next step of the product.
So when I look at Diamonds, I don’t just consider the rewards and the number of tasks.
I look at whether there’s a clear next step left after completion. Being able to guide users from the task page back into the Bedrock path makes this activity feel more like part of the product.
@Bedrock $BR #Bedrock