BitShares Forum
Main => General Discussion => Topic started by: toast on March 03, 2014, 07:55:28 pm
-
I'm making a toolkit for the BTS and larger crypto ecosystem. I'm starting a thread because public expectations are a good commitment strategy.
https://github.com/nmushegian/das
C++ sucks balls for anything other than the core networking/blockchain code and the whole dev setup now scares away newcomes who give up after 30 minutes. Most of the stuff new devs would want to work on are not in the core BTS codebase anyway, they want to quickly and easily interact with the BTS ecosystem.
Ideally Dan will establish a byte-by-byte format for transactions so he can offload building the wallet (misnomer: "transaction maker" - the wallet itself is trivial) onto us. If not there are still a lot of "top-down" software that needs to be written.
This week I plan to deliver:
"das" top-level command routing
"das angel" Angelshare utilities, like a merged btc/pts wallet for holding your AGS and code for looking up snapshot allocations
"das keyring" <- BASIC "wallet" functionality, like just a named list of ECDSA keys and CLI commands for the basic operations on keys
Today I plan to deliver:
* Hopefully most of this week's goal for das keyring.
* Nicely organized super-easy-to-get-started repository
Important stuff in the future:
* BTS X market maker bot
* BTS DNS auction CLI interface
edit: btw "DAS" is distributed autonomous service/system... More friendly and more general that DAC in my opinion.
-
Great initiative, kudos
-
I'm making a toolkit for the BTS and larger crypto ecosystem. I'm starting a thread because public expectations are a good commitment strategy.
C++ sucks balls for anything other than the core networking/blockchain code and the whole dev setup now scares away newcomes who give up after 30 minutes. Most of the stuff new devs would want to work on are not in the core BTS codebase anyway, they want to quickly and easily interact with the BTS ecosystem.
Ideally Dan will establish a byte-by-byte format for transactions so he can offload building the wallet (misnomer: "transaction maker" - the wallet itself is trivial) onto us. If not there are still a lot of "top-down" software that needs to be written.
This week I plan to deliver:
"das" top-level command routing
"das angel" Angelshare utilities, like a merged btc/pts wallet for holding your AGS and code for looking up snapshot allocations
"das keyring" <- BASIC "wallet" functionality, like just a named list of ECDSA keys and CLI commands for the basic operations on keys
Today I plan to deliver:
* Hopefully most of this week's goal for das keyring.
* Nicely organized super-easy-to-get-started repository
Important stuff in the future:
* BTS X market maker bot
* BTS DNS auction CLI interface
edit: btw "DAS" is distributed autonomous service/system... More friendly and more general that DAC in my opinion.
excellent +5%
Does the word "Service" in DAS imply server side code and API or is this still 100% client side? I'd like to learn more. Thanks
-
OP delivers!
https://github.com/nmushegian/das
You can: generate and save named keyrings and generate new named ECDSA keys. Loading will take a bit more work since you can't unmarshal ECDSA curve definitions from the json.
The repo is also set up so that building and testing is super easy.
I will work more on this tonight, I have some good concrete plans for easy, valuable things for das keyring.
-
I'm making a toolkit for the BTS and larger crypto ecosystem. I'm starting a thread because public expectations are a good commitment strategy.
C++ sucks balls for anything other than the core networking/blockchain code and the whole dev setup now scares away newcomes who give up after 30 minutes. Most of the stuff new devs would want to work on are not in the core BTS codebase anyway, they want to quickly and easily interact with the BTS ecosystem.
Ideally Dan will establish a byte-by-byte format for transactions so he can offload building the wallet (misnomer: "transaction maker" - the wallet itself is trivial) onto us. If not there are still a lot of "top-down" software that needs to be written.
This week I plan to deliver:
"das" top-level command routing
"das angel" Angelshare utilities, like a merged btc/pts wallet for holding your AGS and code for looking up snapshot allocations
"das keyring" <- BASIC "wallet" functionality, like just a named list of ECDSA keys and CLI commands for the basic operations on keys
Today I plan to deliver:
* Hopefully most of this week's goal for das keyring.
* Nicely organized super-easy-to-get-started repository
Important stuff in the future:
* BTS X market maker bot
* BTS DNS auction CLI interface
edit: btw "DAS" is distributed autonomous service/system... More friendly and more general that DAC in my opinion.
excellent +5%
Does the word "Service" in DAS imply server side code and API or is this still 100% client side? I'd like to learn more. Thanks
I'm thinking of this a collection of tools for interacting with the ecosystem, most of the tools I can think of would be used as clients, I guess some of the tools might end up being daemons which could be run as a service
-
C++ sucks balls for anything other than the core networking/blockchain code and the whole dev setup now scares away newcomes who give up after 30 minutes. Most of the stuff new devs would want to work on are not in the core BTS codebase anyway, they want to quickly and easily interact with the BTS ecosystem.
+5% nice to see GO deliverables here. I was playing with GO on Ethereum great potential for ease of use.
-
I'm making a toolkit for the BTS and larger crypto ecosystem. I'm starting a thread because public expectations are a good commitment strategy.
https://github.com/nmushegian/das
C++ sucks balls for anything other than the core networking/blockchain code and the whole dev setup now scares away newcomes who give up after 30 minutes. Most of the stuff new devs would want to work on are not in the core BTS codebase anyway, they want to quickly and easily interact with the BTS ecosystem.
Ideally Dan will establish a byte-by-byte format for transactions so he can offload building the wallet (misnomer: "transaction maker" - the wallet itself is trivial) onto us. If not there are still a lot of "top-down" software that needs to be written.
This week I plan to deliver:
"das" top-level command routing
"das angel" Angelshare utilities, like a merged btc/pts wallet for holding your AGS and code for looking up snapshot allocations
"das keyring" <- BASIC "wallet" functionality, like just a named list of ECDSA keys and CLI commands for the basic operations on keys
Today I plan to deliver:
* Hopefully most of this week's goal for das keyring.
* Nicely organized super-easy-to-get-started repository
Important stuff in the future:
* BTS X market maker bot
* BTS DNS auction CLI interface
edit: btw "DAS" is distributed autonomous service/system... More friendly and more general that DAC in my opinion.
This is very encouraging information.
What is the BTS X market maker bot? Can you reveal more about this? Will it be configurable?
-
+1 Great work Toast!
-
C++ sucks balls for anything other than the core networking/blockchain code and the whole dev setup now scares away newcomes who give up after 30 minutes. Most of the stuff new devs would want to work on are not in the core BTS codebase anyway, they want to quickly and easily interact with the BTS ecosystem.
I have addressed this same issue on the Technical Support board.
https://bitsharestalk.org/index.php?topic=3397.0
(+5% for taking this initiative)
-
What is the BTS X market maker bot? Can you reveal more about this? Will it be configurable?
Yes, the idea is you give it your locally trusted price feeds and some parameters and it trades for you by your rules.
-
nice! :) +5%
-
C++11 does not suck, and will be around much longer then go. Having said that, nice to see someone deliver on something.
How does this compare to:
https://github.com/BitShares/bitshares_toolkit
-
+5%
Great job Toast!