Author Topic: Next Documentation Efforts [poll]  (Read 4940 times)

0 Members and 1 Guest are viewing this topic.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Is there a up-to-date white paper of DPOS itself?
It would be useful when comparing to the competitors' E.G. IBM's OpenLedger, Linux Foundation's OpenLedger, Eth and so.
Sorry if this is a stupid question.
Not a stupid questions .. and we *STILL* lack this whitepaper ..
Any help/assistance would be greatly appreciated!
It's sad that bm have no time to write it down. Always rushing on implementing things and/or think about new ideas.
I am not good at writing at all, I can help check/improve if there is a draft.
BitShares committee member: abit
BitShares witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Is there a up-to-date white paper of DPOS itself?
It would be useful when comparing to the competitors' E.G. IBM's OpenLedger, Linux Foundation's OpenLedger, Eth and so.
Sorry if this is a stupid question.
Not a stupid questions .. and we *STILL* lack this whitepaper ..
Any help/assistance would be greatly appreciated!

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Is there a up-to-date white paper of DPOS itself?
It would be useful when comparing to the competitors' E.G. IBM's OpenLedger, Linux Foundation's OpenLedger, Eth and so.
Sorry if this is a stupid question.
BitShares committee member: abit
BitShares witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
For those that haven't noticed, there is a bunch of updates (including one big update which I wrote today):

    16/01/12 Assets/Tokens, Creating a UIA manually Creating a MPA manually, Frequently Asked Questions, Privatized BitAssets, Publishing a Feed, Prediction Markets, Creating a Prediction Market, Closing/Settling a Prediction Market
    16/01/07 User Issued Assets, Creating a new UIA, Creating a UIA manually
    16/01/06 Change the Signing Key of your Witness
    15/12/21 Workers / Budget Items, Fee Backed Asset, Funding Your Ideas, BitShares Improvement Proposal
    15/12/18 Whitepapers: Release Candiate for the BitShares: General Overview whitepaper
    15/12/04 Permissions, Proposed Transactions

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
@ xeroc, I think it would be most beneficial to provide documentation on how to build a transaction that requires multiple signatures, propose the transaction, and then have it signed by all active authority accounts. Is this something you would be up for?

The most important feature that we are not using right now is multi sig transactions.
absoluteley .. it's on my list ...

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
@ xeroc, I think it would be most beneficial to provide documentation on how to build a transaction that requires multiple signatures, propose the transaction, and then have it signed by all active authority accounts. Is this something you would be up for?

The most important feature that we are not using right now is multi sig transactions.
absoluteley .. it's on my list ... and I hope to see this also implemented in the GUI soonish :)

clout

  • Guest
@ xeroc, I think it would be most beneficial to provide documentation on how to build a transaction that requires multiple signatures, propose the transaction, and then have it signed by all active authority accounts. Is this something you would be up for?

The most important feature that we are not using right now is multi sig transactions.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
There is an issue about this .. I need to reread the code .. but I think the tutorial is correct ..
https://github.com/cryptonomex/graphene/issues/467
https://github.com/cryptonomex/graphene/commit/7a5c5c476d9762cbba1d745447191523ca5cd601 

The patch is on a different branch, hence propose_builder_transaction2 is not yet available

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Since my last post here, I made some considerable improvements and wrote some more articles:

15/12/03 Manually Construct Any Transaction, Proposing a Transaction
15/12/03 Tutorials, Confidential Transfers, Committee, Claim Worker Pay, Shareholder, Workers / Budget Items, Often used API Calls, Wallet Merchant Protocol, Wallet Login Protocol
15/11/30 Margin call mechanics
15/11/26 First Steps for End-Users, Things you should know, Assets/Tokens
15/11/23 User Guide updates: Transactions and Operations, Decentralized Exchange, Security
15/11/13 Refactoring, updates for: Integration Guide
15/11/10 Added MUSE blockchain: MUSE

For those that haven't notices .. you can now also reach it via docs.bitshares.ORG!

Cheers

Nice.  I just took a look. 

I have a question.  Is "add_operation_to_builder_transaction" still valid or is it replaced by "add_operation_to_builder_transaction2"?
You are mixing up
 * propose_builder_transaction and
 * propose_builder_transaction2 (will be available in a future release)

I never ran across a "add_operation_to_builder_transaction2" .. and it really only puts JSON objects together ... don't see a need to another implementation :)

You are right. My bad. Typo mistake with copy-and-paste too fast. I meant "  Is "propose_builder_transaction" still valid or is it replaced by "propose_builder_transaction2"?"


propose_builder_transaction was mentioned in the document.  Should it be removed if it is no longer valid?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Since my last post here, I made some considerable improvements and wrote some more articles:

15/12/03 Manually Construct Any Transaction, Proposing a Transaction
15/12/03 Tutorials, Confidential Transfers, Committee, Claim Worker Pay, Shareholder, Workers / Budget Items, Often used API Calls, Wallet Merchant Protocol, Wallet Login Protocol
15/11/30 Margin call mechanics
15/11/26 First Steps for End-Users, Things you should know, Assets/Tokens
15/11/23 User Guide updates: Transactions and Operations, Decentralized Exchange, Security
15/11/13 Refactoring, updates for: Integration Guide
15/11/10 Added MUSE blockchain: MUSE

For those that haven't notices .. you can now also reach it via docs.bitshares.ORG!

Cheers

Nice.  I just took a look. 

I have a question.  Is "add_operation_to_builder_transaction" still valid or is it replaced by "add_operation_to_builder_transaction2"?
You are mixing up
 * propose_builder_transaction and
 * propose_builder_transaction2 (will be available in a future release)

I never ran across a "add_operation_to_builder_transaction2" .. and it really only puts JSON objects together ... don't see a need to another implementation :)

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Since my last post here, I made some considerable improvements and wrote some more articles:

15/12/03 Manually Construct Any Transaction, Proposing a Transaction
15/12/03 Tutorials, Confidential Transfers, Committee, Claim Worker Pay, Shareholder, Workers / Budget Items, Often used API Calls, Wallet Merchant Protocol, Wallet Login Protocol
15/11/30 Margin call mechanics
15/11/26 First Steps for End-Users, Things you should know, Assets/Tokens
15/11/23 User Guide updates: Transactions and Operations, Decentralized Exchange, Security
15/11/13 Refactoring, updates for: Integration Guide
15/11/10 Added MUSE blockchain: MUSE

For those that haven't notices .. you can now also reach it via docs.bitshares.ORG!

Cheers

Nice.  I just took a look. 

I have a question.  Is "add_operation_to_builder_transaction" still valid or is it replaced by "add_operation_to_builder_transaction2"?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Since my last post here, I made some considerable improvements and wrote some more articles:

15/12/03 Manually Construct Any Transaction, Proposing a Transaction
15/12/03 Tutorials, Confidential Transfers, Committee, Claim Worker Pay, Shareholder, Workers / Budget Items, Often used API Calls, Wallet Merchant Protocol, Wallet Login Protocol
15/11/30 Margin call mechanics
15/11/26 First Steps for End-Users, Things you should know, Assets/Tokens
15/11/23 User Guide updates: Transactions and Operations, Decentralized Exchange, Security
15/11/13 Refactoring, updates for: Integration Guide
15/11/10 Added MUSE blockchain: MUSE

For those that haven't notices .. you can now also reach it via docs.bitshares.ORG!

Cheers

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
This thread - ttps://bitsharestalk.org/index.php/topic,20267.0/topicseen.html goes to show a documentation on securing wallet/fund is important and very much needed.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Working on the backup/coldstorage/security aspects now

edit: seems that coldstorage infrastructure needs some more time ...
can brain key consider as a cold-storage way ? 

Yes .. if you have never manually imported a private key .. all your accounts can be recovered via brain key..

you can give it a try an create a new wallet from the brain wallet of your existing wallet

Offline BTSdac

  • Hero Member
  • *****
  • Posts: 1219
    • View Profile
  • BitShares: K1
Working on the backup/coldstorage/security aspects now

edit: seems that coldstorage infrastructure needs some more time ...
can brain key consider as a cold-storage way ? 
github.com :pureland
BTS2.0 API :ws://139.196.37.179:8091
BTS2.0 API 数据源ws://139.196.37.179:8091