maybe 100% delegate should burn some progress on to the wall of delegate id

Started by sudo, January 26, 2015, 08:01:40 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

matt608

Quote from: ripplexiaoshan on January 27, 2015, 04:40:32 PM
Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

BunkerChainLabs-DataSecurityNode

Quote from: ripplexiaoshan on January 27, 2015, 04:40:32 PM
Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

I saw two respond in the thread and suggested there needed to be improvements for the burn to ensure proper identification. You might have missed them, but they are there. :)

Besides this, during the last Beyond Bitcoin meeting Friday this was discussed with BM. It was suggested a possible framework for reporting could be created to standardize it. Makes sense.

However, every project is different in the frequency of their updates. Do you really want daily updates that basically say.. debuged this, 50 lines of code today, did this, did that each day? For some progress might be measured in strategic meetings and events that span months. So while the framework would make total sense so that we can index and keep track of it all, the frequency would really depend on what it requires. I think it is fair to have the delegate from the start declare their planned update frequency. If this is found deficient then it can be brought up. If still not satisfactory then they start to lose votes obviously.

Just a few things to consider... transparency is a no brainer.. efficiently executing on how that is delivered without overburdening will take some finesse.
+-+-+-+-+-+-+-+-+-+-+
[url="//www.peerplays.com"]www.Peerplays.com[/url] | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

sudo

visit bitsharestalk.org is so slow  make me mad. :'( :'( :'(



at least  delegate can  paste  the URL of their topic  on the wall

ripplexiaoshan

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...
BTS committee member:jademont

sudo


Rune

I like this idea. Forum reports would be fine as well, we just need more transparency from our delegates across the board.

xiahui135

good idea.
and we have these delegates. it is reasonable to measure what they are doing. And hope some delegate will lead to do that, to compete some delegates out.

sudo

Quote from: xeroc on January 26, 2015, 11:16:22 AM
This can be achieved once non-TITAN transactions are used and the owner of the balance_id that acutally spends the burn can be linked to an account (read: is the BTS address of the owner/signing key of a delegate)

blockchain_get_account_wall can show the signer
but GUI can't

maybe  GUI can  list two part or three column

the id owner himself
the  Non-anonymous
the Anonymous


>> help blockchain_get_account_wall

Usage:
blockchain_get_account_wall [account_name]                                                            returns all burn records associated with an account
returns all burn records associated with an account

Parameters:
  account_name (account_name, optional, defaults to ""): the name of the account to fetch the burn records for

Returns:
  burn_records

aliases: wall

xeroc

This can be achieved once non-TITAN transactions are used and the owner of the balance_id that acutally spends the burn can be linked to an account (read: is the BTS address of the owner/signing key of a delegate)

liondani

Quote from: xeroc on January 26, 2015, 10:28:58 AM
Quote from: liondani on January 26, 2015, 10:24:20 AM
+5% +5% +5%

very good idea!!!
that ensures that these updates will never get lost (blockchain) and anybody can review them at any point in time very easy!
Simultaneously  anybody should copy/paste it to a personal progress/report thread on this forum for max exposure...
I like that idea too .. +5%

That way wall messages also function as a kind of contract :)

but how can we ensure that a message (about progress etc.) is not burned from a third-party/spammer instead the real owner of the delegate id?
I propose a future/option that allows us to make public the id that burned the message (example when we burn to our own account)...
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

xeroc

Quote from: liondani on January 26, 2015, 10:24:20 AM
+5% +5% +5%

very good idea!!!
that ensures that these updates will never get lost (blockchain) and anybody can review them at any point in time very easy!
Simultaneously  anybody should copy/paste it to a personal progress/report thread on this forum for max exposure...
I like that idea too .. +5%

That way wall messages also function as a kind of contract :)

liondani

 +5% +5% +5%

very good idea!!!
that ensures that these updates will never get lost (blockchain) and anybody can review them at any point in time very easy!
Simultaneously  anybody should copy/paste it to a personal progress/report thread on this forum for max exposure...
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

sudo



cgafeng

BTC:1EYwcZ9cYVj6C9LMLafdcjK9wicVMDV376