Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - puppies

Pages: [1] 2 3
1
Technical Support / webwallet on ios
« on: April 01, 2016, 06:39:29 am »
my webwallet used to work in safari on my iphone.  Now its just a loading screen that never finishes loading.  Is there a trick to getting the wallet to load properly on ios?  I have tried to use the older version of npm, and of course have run npm install in the ios folder.  In short I have tried building the newer wallets exactly as I used to build the old wallets.  The only thing I haven't tried is to build an older gui to see if that what is needed. 

Any ideas?

3
General Discussion / Simulated proof of work
« on: March 31, 2016, 06:05:57 pm »
What if there was a way to use the massive resources used to secure proof of work coins to help solve the worlds problems?  As you probably know you cannot secure a proof of work coin with something like protein folding.  In order to secure a coin the work that is done needs to be unpredictable.  If only there were a better way.

What if we simulated a pow coin on the BitShares network, and generated new coins based upon users solving computation problems that actually serve a greater purpose than securing a network?  Since we don't require pow to secure our network we could reward miners for helping any number of distributed computation programs.  Here is wikipedias list of distributed computation projects.  https://en.wikipedia.org/wiki/List_of_distributed_computing_projects  We could launch a coin for each or any of these projects.

I just thought of this today, and wanted to get some input on it.  Does anyone have any experience with any of these distributed computing projects?  Any ideas on how we could have users prove not only that they are contributing, but also how much they are contributing.  How do we take something like this http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userstats and have people prove that they are contributing.  It could be as simple as a script that runs on the asset issuers node and issues assets once a day, or as involved as a smart contract that issues a special type of asset automatically.  We could require that they run a full node, thus increasing the network resilience, or let them report their proof of work through a light client.

If we can convince one of these big projects that we could help get them users, they might be willing to help us integrate. 

Does anyone else think this could be a major coup for bitshares or am I deluding myself?

There is already curecoin but it looks like they are attempting to merge sha256 with fold at home, we have no need for pow for security so we could go further and have all computation going towards a distributed computing project.
https://foldingforum.org/viewtopic.php?f=16&t=25254&start=30
https://www.curecoin.net/

What do you think? 

4
Technical Support / help with faucet
« on: March 21, 2016, 08:24:50 pm »
Hey everyone.  I have a webwallet and faucet set up at https://dele-puppy.com.  I cannot get referral links to work properly.  My faucet will register new accounts just fine, but adding the ?r=account-name doesn't seem to make a difference in the new account.  I am not looking to get into the faucet business or to compete with OL at all.  I am running both the wallet and the faucet as a service for the community.  The wallet is based in San Francisco and seems to offer better performance to some in our community.  The faucet can be used as a backup when OL is not functioning.  When I attempt to register a new account with https://dele-puppy.com/?r=dele-puppy my production log shows
Code: [Select]
I, [2016-03-21T16:05:57.040050 #15512]  INFO -- : Started POST "/api/v1/accounts" for <redacted IP> at 2016-03-21 16:05:57 -0400
I, [2016-03-21T16:05:57.050940 #15512]  INFO -- : Processing by Api::V1::AccountsController#create as JSON
I, [2016-03-21T16:05:57.051096 #15512]  INFO -- :   Parameters: {"account"=>{"name"=>"puppies-test-2", "owner_key"=>"BTS59wWKYExLCfAnU7LdpWHHrVjaA5XDgTXjhofcRw7RhcomTSYcC", "active_key"=>"BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1", "memo_key"=>"BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1", "refcode"=>nil}}
D, [2016-03-21T16:05:57.087642 #15512] DEBUG -- :   #[1m#[35m (0.4ms)#[0m  BEGIN
D, [2016-03-21T16:05:57.126459 #15512] DEBUG -- :   #[1m#[36mBtsAccount Exists (18.0ms)#[0m  #[1mSELECT  1 AS one FROM `bts_accounts` WHERE `bts_accounts`.`remote_ip` = BINARY <redacted IP> AND (created_at > '2016-03-21 16:00:57') LIMIT 1#[0m
I, [2016-03-21T16:05:57.128353 #15512]  INFO -- : ---- Registering account: 'puppies-test-2' BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1/BTS59wWKYExLCfAnU7LdpWHHrVjaA5XDgTXjhofcRw7RhcomTSYcC referrer:
I, [2016-03-21T16:05:57.129134 #15512]  INFO -- : call: [0, "get_account", ["puppies-test-2"]]
E, [2016-03-21T16:05:57.235216 #15512] ERROR -- : Websocket RPC Error: {"code"=>1, "message"=>"10 assert_exception: Assert Exception\nrec && rec->name == account_name_or_id: \n    {}\n    th_a  wallet.cpp:596 get_account", "data"=>{"code"=>10, "name"=>"assert_exception", "message"=>"Assert Exception", "stack"=>[{"context"=>{"level"=>"error", "file"=>"wallet.cpp", "line"=>596, "method"=>"get_account", "hostname"=>"", "thread_name"=>"th_a", "timestamp"=>"2016-03-21T20:05:57"}, "format"=>"rec && rec->name == account_name_or_id: ", "data"=>{}}]}}
I, [2016-03-21T16:05:57.236168 #15512]  INFO -- : call: [0, "register_account", ["puppies-test-2", "BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1", "BTS59wWKYExLCfAnU7LdpWHHrVjaA5XDgTXjhofcRw7RhcomTSYcC", "dele-puppy-reg", "dele-puppy-reg", 0, true]]
D, [2016-03-21T16:05:57.624972 #15512] DEBUG -- : {"ref_block_num"=>54133, "ref_block_prefix"=>3479785826, "expiration"=>"2016-03-21T20:06:27", "operations"=>[[5, {"fee"=>{"amount"=>1483385, "asset_id"=>"1.3.0"}, "registrar"=>"1.2.101323", "referrer"=>"1.2.101323", "referrer_percent"=>0, "name"=>"puppies-test-2", "owner"=>{"weight_threshold"=>1, "account_auths"=>[], "key_auths"=>[["BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1", 1]], "address_auths"=>[]}, "active"=>{"weight_threshold"=>1, "account_auths"=>[], "key_auths"=>[["BTS59wWKYExLCfAnU7LdpWHHrVjaA5XDgTXjhofcRw7RhcomTSYcC", 1]], "address_auths"=>[]}, "options"=>{"memo_key"=>"BTS59wWKYExLCfAnU7LdpWHHrVjaA5XDgTXjhofcRw7RhcomTSYcC", "voting_account"=>"1.2.5", "num_witness"=>0, "num_committee"=>0, "votes"=>[], "extensions"=>[]}, "extensions"=>{}}]], "extensions"=>[], "signatures"=>["1f681f1e599dc9a77d4e3f5bd12acb1e4a658cde2b1b40fef403b46a65cd5b918424fdac871aa6f73f60e39675ed30fae2966c4ba1ffc0a6e465da9fdec6ca77c5"]}
D, [2016-03-21T16:05:57.640035 #15512] DEBUG -- :   #[1m#[35mSQL (11.8ms)#[0m  INSERT INTO `bts_accounts` (`name`, `owner_key`, `active_key`, `memo_key`, `remote_ip`, `created_at`, `updated_at`) VALUES ('puppies-test-2', 'BTS59wWKYExLCfAnU7LdpWHHrVjaA5XDgTXjhofcRw7RhcomTSYcC', 'BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1', 'BTS5abB7845TM3GSq1ExiWDEU7wKZFEfZJTYTDQ94h4cnZioiMbW1', <redacted IP>, '2016-03-21 20:05:57', '2016-03-21 20:05:57')
D, [2016-03-21T16:05:57.643623 #15512] DEBUG -- :   #[1m#[36m (2.0ms)#[0m  #[1mCOMMIT#[0m
I, [2016-03-21T16:05:57.654643 #15512]  INFO -- :   Rendered api/v1/accounts/show.json.jbuilder (5.0ms)
I, [2016-03-21T16:05:57.655155 #15512]  INFO -- : Completed 201 Created in 604ms (Views: 10.9ms | ActiveRecord: 41.2ms)
I, [2016-03-21T16:07:23.065115 #15512]  INFO -- : Started POST "/" for 5.217.143.35 at 2016-03-21 16:07:23 -0400
F, [2016-03-21T16:07:23.066696 #15512] FATAL -- :
ActionController::RoutingError (No route matches [POST] "/"):
  vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
  vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  vendor/bundle/ruby/2.2.0/gems/railties-4.2.4/lib/rails/rack/logger.rb:38:in `call_app'
  vendor/bundle/ruby/2.2.0/gems/railties-4.2.4/lib/rails/rack/logger.rb:20:in `block in call'
  vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/tagged_logging.rb:68:in `block in tagged'
  vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/tagged_logging.rb:26:in `tagged'
  vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/tagged_logging.rb:68:in `tagged'
  vendor/bundle/ruby/2.2.0/gems/railties-4.2.4/lib/rails/rack/logger.rb:20:in `call'
  vendor/bundle/ruby/2.2.0/gems/actionpack-4.2.4/lib/action_dispatch/middleware/request_id.rb:21:in `call'
  vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
  vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
  vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.4/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
  vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
  vendor/bundle/ruby/2.2.0/gems/railties-4.2.4/lib/rails/engine.rb:518:in `call'
  vendor/bundle/ruby/2.2.0/gems/railties-4.2.4/lib/rails/application.rb:165:in `call'
  passenger (5.0.24) src/ruby_supportlib/phusion_passenger/rack/thread_handler_extension.rb:97:in `process_request'
  passenger (5.0.24) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:160:in `accept_and_process_next_request'
  passenger (5.0.24) src/ruby_supportlib/phusion_passenger/request_handler/thread_handler.rb:113:in `main_loop'
  passenger (5.0.24) src/ruby_supportlib/phusion_passenger/request_handler.rb:416:in `block (3 levels) in start_threads'
  passenger (5.0.24) src/ruby_supportlib/phusion_passenger/utils.rb:113:in `block in create_thread_and_abort_on_exception'
my faucet.yml is
Code: [Select]
cli_wallet_connection: ws://localhost:8099
registrar_account: dele-puppy-reg
referrer_percent: 80
refcode_prefix: F01

default_url: localhost
default_port: 3000

exception_notification:
  sender_address: [email protected]
  exception_recipients: [email protected]

smtp:
  address: address
  user_name: user
  password: password

Any idea what is preventing referrals fAny more information that could help figure this out?  It is not really an important issue.  As I said I don't really want lots of people using my faucet unless absolutely needed.  I am a noob at the running a website thing, and would like to learn more though.

Thanks.

5
We previously had a poll https://bitsharestalk.org/index.php/topic,21218.0.html which showed low turnout, but rather wide support for transferring the bitassets collected by the fee pool to a separate account called committee-trade to sell them for bts.  The OP was

The committee has withdrawn the fees collected by the fee pools for our committee owned assets.  We have not yet sold these bitassets into the market.  This is the first of a number of polls to help determine the best way to accomplish this. 

The issue we have run into is that it is impossible to do anything with the committee account in real time.  Even if we got 51% of the committee on at the same time there is a 1 hour review period required for all committee proposals.  Realistically in order to get 51% of the committee to vote on something would take more like at least 12 hours.  The price of these bitassets can change fast, and the price which we set could be completely inappropriate by the time the proposal passes.  This is even more of a risk if we need to cancel a market order.  I think that using the committee account risks causing more damage to the peg than good.

To combat this I have created a new account http://cryptofresh.com/u/committee-trade It has owner permissions set to the committee, so the committee still has control of the account.  The active authority is currently set to myself, bhuz, abit, and xeroc.  abit and xeroc have not agreed to join in, I added them because I don't think they will mind.  Bhuz volunteered to help.  It is currently set as a 2 of 4 multi sig.  Because the committee account owns this account the committee can adjust the active authorities as it sees fit. 

I propose that we iron out exactly who will have active authority on this account, set the permissions properly, and transfer the bitassets held by the committee-account to committee-trade.  Committee-trade can then sell these assets in real time.  We could even devise a simple bot that will set sell walls at a certain percentage over feed price.

The committee currently owns

USD   6,910
EUR   10.24
GOLD   0.00381
SILVER   3.09
CNY   7,870
BTC   0.476

The consensus from earlier conversations was that we would sell these assets into their BTS market at a certain percentage above the peg.  There will be a separate poll to determine the rate above peg which we should target.  What we should do with the BTS received from these sales, is also a separate conversation.  I would like to keep this conversation about whether or not we should use the committee-trade account or the committee-account account to process these sales.  Also if anyone with good knowledge of the cli_wallet wants to step and help by becoming a multi sig active auth please let us know.

Yesterday we adjusted the active authority on the cOmmittee-trade account to add bitcube, and to increase the required weight to 3 of 5.  This should have required the owner authority of the account, which in this case is the committee.  Instead we discovered a bug.  The active authority can be adjusted by the active authority.  It only required abit and I to add bitcube, and to increase the threshold required.  Abit has filed an issue https://github.com/cryptonomex/graphene/issues/556 

This bug does not increase the risk of having these funds stolen while they are being traded.  This would require that of bhuz, bitcube, abit, xeroc, and myself three of us colluded together to steal these funds.  It does however increase the chance that the account can be stolen.  It effectively removes the ability of the committee to add or remove active authorizations to the account.  This instead needs to be done by the existing active authorities until this bug is fixed.

Please vote for what you think.

6
General Discussion / [poll] why did you upgrade to life time membership
« on: February 07, 2016, 05:31:10 am »
I would like some input from those of you that have upgraded your account to life time membership.  What was your motivation?  You may vote for up to 3 options, and may change your vote at any time.

7
Technical Support / Setting up a faucet
« on: February 03, 2016, 06:06:06 pm »
I am working on setting up a faucet.  I am running into an error at the mina deploy stage.  I get
Code: [Select]
-----> Migrating database
       rake aborted!
       Errno::ENOENT: No such file or directory @ rb_sysopen - /www/tmp/build-14545217352693/config/faucet.yml
       /www/tmp/build-14545217352693/config/application.rb:9:in `read'
       /www/tmp/build-14545217352693/config/application.rb:9:in `<top (required)>'
       /www/tmp/build-14545217352693/Rakefile:4:in `require'
       /www/tmp/build-14545217352693/Rakefile:4:in `<top (required)>'
       (See full trace by running task with --trace)
 !     ERROR: Deploy failed.
-----> Cleaning up build
       Unlinking current
       OK

 !     Command failed.
       Failed with status 1 (19)
Any ideas?

8
I just got a new laptop.  At this point I am running Ubuntu 15.10 due to 14.04 not having support for my wireless card.  I am running into a a bit of an issue with launching my local clients though.  I can run my witness_node, and it sync and replays just fine.  The issue is when I attempt to connect a cli_wallet to it.  My cli_wallet freezes, and it crashes my witness_node.  Has anyone run on 15.10.  Is there anything extra that needs to be done?  Anyone run into this cli_wallet connection kills the witness_node?  The gdb bt is below.

Code: [Select]
1641836ms th_a       database_api.cpp:186          database_api_impl    ] creating database api 760714960

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4973700 (LWP 32437)]
0x0000000000f4f558 in websocketpp::processor::hybi13<fc::http::detail::asio_with_stub_log>::consume(unsigned char*, unsigned long, std::error_code&) ()
(gdb) bt
#0  0x0000000000f4f558 in websocketpp::processor::hybi13<fc::http::detail::asio_with_stub_log>::consume(unsigned char*, unsigned long, std::error_code&) ()
#1  0x0000000000f2b189 in websocketpp::connection<fc::http::detail::asio_with_stub_log>::handle_read_frame(std::error_code const&, unsigned long) ()
#2  0x0000000000f00eb8 in websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config>::handle_async_read(boost::system::error_code const&, unsigned long) ()
#3  0x0000000000f18a25 in boost::asio::detail::completion_handler<boost::asio::detail::binder2<std::_Bind<std::_Mem_fn<void (websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config>::*)(boost::system::error_code const&, unsigned long)> (std::shared_ptr<websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config> >, std::_Placeholder<1>, std::_Placeholder<2>)>, boost::system::error_code, unsigned long> >::do_complete(boost::asio::detail::task_io_service*, boost::asio::detail::task_io_service_operation*, boost::system::error_code const&, unsigned long) ()
#4  0x0000000000f18cce in void boost::asio::detail::strand_service::dispatch<boost::asio::detail::binder2<std::_Bind<std::_Mem_fn<void (websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config>::*)(boost::system::error_code const&, unsigned long)> (std::shared_ptr<websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config> >, std::_Placeholder<1>, std::_Placeholder<2>)>, boost::system::error_code, unsigned long> >(boost::asio::detail::strand_service::strand_impl*&, boost::asio::detail::binder2<std::_Bind<std::_Mem_fn<void (websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config>::*)(boost::system::error_code const&, unsigned long)> (std::shared_ptr<websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config> >, std::_Placeholder<1>, std::_Placeholder<2>)>, boost::system::error_code, unsigned long>&) ()
#5  0x0000000000f18e08 in std::_Function_handler<void (boost::system::error_code const&, unsigned long), boost::asio::detail::wrapped_handler<boost::asio::io_service::strand, std::_Bind<std::_Mem_fn<void (websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config>::*)(boost::system::error_code const&, unsigned long)> (std::shared_ptr<websocketpp::transport::asio::connection<fc::http::detail::asio_with_stub_log::transport_config> >, std::_Placeholder<1>, std::_Placeholder<2>)>, boost::asio::detail::is_continuation_if_running> >::_M_invoke(std::_Any_data const&, boost::system::error_code const&, unsigned long&&) ()
#6  0x0000000000f1a1bd in boost::asio::detail::read_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::mutable_buffers_1, boost::asio::detail::transfer_at_least_t, websocketpp::transport::asio::custom_alloc_handler<std::function<void (boost::system::error_code const&, unsigned long)> > >::operator()(boost::system::error_code const&, unsigned long, int) ()
#7  0x0000000000f1a7c0 in boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::asio::detail::read_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::mutable_buffers_1, boost::asio::detail::transfer_at_least_t, websocketpp::transport::asio::custom_alloc_handler<std::function<void (boost::system::error_code const&, unsigned long)> > > >::do_complete(boost::asio::detail::task_io_service*, boost::asio::detail::task_io_service_operation*, boost::system::error_code const&, unsigned long) ()
#8  0x0000000000f5fa8b in fc::asio::default_io_service_scope::default_io_service_scope()::{lambda()#1}::operator()() const ()
#9  0x0000000001098845 in thread_proxy ()
#10 0x00007ffff7bc26aa in start_thread (arg=0x7ffff4973700) at pthread_create.c:333
#11 0x00007ffff6c4aeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb)

9
For the sake of argument lets assume that we have all agreed on the need to sell the collected assets owned by the committee-account.  These assets are.
USD   6,910
EUR   10.24
GOLD   0.00381
SILVER   3.09
CNY   7,870
BTC   0.476
What rate above feed do you believe would be best?  Please vote.  If your exact proposal is not listed please vote for the closest to the percentage you would like.  If instead you believe that we should take a completely different tack, please let us know.

10
The committee has withdrawn the fees collected by the fee pools for our committee owned assets.  We have not yet sold these bitassets into the market.  This is the first of a number of polls to help determine the best way to accomplish this. 

The issue we have run into is that it is impossible to do anything with the committee account in real time.  Even if we got 51% of the committee on at the same time there is a 1 hour review period required for all committee proposals.  Realistically in order to get 51% of the committee to vote on something would take more like at least 12 hours.  The price of these bitassets can change fast, and the price which we set could be completely inappropriate by the time the proposal passes.  This is even more of a risk if we need to cancel a market order.  I think that using the committee account risks causing more damage to the peg than good.

To combat this I have created a new account http://cryptofresh.com/u/committee-trade It has owner permissions set to the committee, so the committee still has control of the account.  The active authority is currently set to myself, bhuz, abit, and xeroc.  abit and xeroc have not agreed to join in, I added them because I don't think they will mind.  Bhuz volunteered to help.  It is currently set as a 2 of 4 multi sig.  Because the committee account owns this account the committee can adjust the active authorities as it sees fit. 

I propose that we iron out exactly who will have active authority on this account, set the permissions properly, and transfer the bitassets held by the committee-account to committee-trade.  Committee-trade can then sell these assets in real time.  We could even devise a simple bot that will set sell walls at a certain percentage over feed price.

The committee currently owns

USD   6,910
EUR   10.24
GOLD   0.00381
SILVER   3.09
CNY   7,870
BTC   0.476

The consensus from earlier conversations was that we would sell these assets into their BTS market at a certain percentage above the peg.  There will be a separate poll to determine the rate above peg which we should target.  What we should do with the BTS received from these sales, is also a separate conversation.  I would like to keep this conversation about whether or not we should use the committee-trade account or the committee-account account to process these sales.  Also if anyone with good knowledge of the cli_wallet wants to step and help by becoming a multi sig active auth please let us know.

11
General Discussion / Adjusted prediction market
« on: January 18, 2016, 04:48:06 pm »
I created a prediction market to test creation, and settling.  It is asset BTCPREDICT.  I originally set it as an over under on the price of bitcoin at $450.  Bitcoin then decided to drop $90 and rebound $30.  As no bets have been matched, I have changed the over under price to $380.  I will almost certainly just end up selling some to myself before I settle the asset, but I wanted to be clear about the changes to the asset in case anyone does decide to buy in.

12
Liquidity is one of our greatest issues.  One possible solution would be to use the power to dilute to create more bitassets to hold the peg. 

We could create a worker proposal that sends funds to the committee account.  We could design a bot that will short assets into existence and sell them at a prescribed rate above the peg.  This would still require a majority of committee members to approve each transaction.  this approval could also be automated.

We could through the committee have a market maker that holds the peg of smartcoins to within a couple of percentage points of the feed price.  We could even branch out into other derivatives such as individual stocks. 

Once again I am looking for community input.  Please argue your point.  If there are specific parameters that would be deal breakers please mention them as well.   You may change your vote if you have changed your mind.

Thank you for your input.

13
I was looking through the docs, and I found the section on creating vesting balance objects.  Wouldn't that be a better way of distributing the revenue of a fee backed asset than with a buybay?  What are the fees to deposit to a vesting object?  Could a FBA deposit to the same VBO that is used for cashback, or would each FBA need to create its own VBO?  We could require that a potential hodler of a FBA registers a VBO for it.  95bts once, plus 2bts per withdrawal seems like a better deal than having to place orders for a buyback. 

Code: [Select]

        Public Members

        uint64_t fee

            the cost to register the cheapest non-free account

struct vesting_balance_create_operation
    #include <vesting.hpp>

    Create a vesting balance.

    The chain allows a user to create a vesting balance. Normally, vesting balances are created automatically as part of cashback and worker operations. This operation allows vesting balances to be created manually as well.

    Manual creation of vesting balances can be used by a stakeholder to publicly demonstrate that they are committed to the chain. It can also be used as a building block to create transactions that function like public debt. Finally, it is useful for testing vesting balance functionality.

    Return
        ID of newly created vesting_balance_object

    Public Members

    account_id_type creator

        Who provides funds initially.

    account_id_type owner

        Who is able to withdraw the balance.

class vesting_balance_object
    #include <vesting_balance_object.hpp>

    Vesting balance object is a balance that is locked by the blockchain for a period of time.

    Public Functions

    void deposit(const fc::time_point_sec &now, const asset &amount)

        Deposit amount into vesting balance, requiring it to vest before withdrawal.

    void deposit_vested(const fc::time_point_sec &now, const asset &amount)

        Deposit amount into vesting balance, making the new funds vest immediately.

    void withdraw(const fc::time_point_sec &now, const asset &amount)

        Used to remove a vesting balance from the VBO. As well as the balance field, coin_seconds_earned and coin_seconds_earned_last_update fields are updated.

        The money doesn’t “go” anywhere; the caller is responsible for crediting it to the proper account.

    asset get_allowed_withdraw(const time_point_sec &now) const

        Get amount of allowed withdrawal.

    Public Members

    account_id_type owner

        Account which owns and may withdraw from this vesting balance.

    asset balance

        Total amount remaining in this vesting balance Includes the unvested funds, and the vested funds which have not yet been withdrawn

    vesting_policy policy

        The vesting policy stores details on when funds vest, and controls when they may be withdrawn.

struct vesting_balance_withdraw_operation
    #include <vesting.hpp>

    Withdraw from a vesting balance.

    Withdrawal from a not-completely-mature vesting balance will result in paying fees.

    Return
        Nothing


Am I missing something?

14
There has been a lot of discussion about improving liquidity recently.  I wanted to get some input on possible actions the committee account could take. 

Option 1.  The committee could sell the bitassets collected by the fee pool back into the market.
Through the fee pool the committee is currently long 6910 USD, 7860 CNY, and .473BTC.  In the case of USD that is over 6% of total supply.

Option 2.  The committee could use the bts procured from selling the assets in option 1 to short more of the asset into existence.  Assuming a 3x collateral ratio, the committee could short an extra 2300USD into existence. 

Option 3.  The committee could receive funds from a worker proposal, and use those to short a larger amount of an asset into existence.  We could for example create 50k USD, and 50 BTC.

This is not an endorsement of any of these actions.  I am trying to collect community input. 

15
Freebie / funding my sharebot account.
« on: December 24, 2015, 07:17:58 pm »
Hello all

I sent 10k bts to my sharebot account about 3 hours ago, but I haven't seen the credit yet.  I copy pasted the memo field, and I am pretty sure I did it right.  Is there an issue with the bot, or did I make a mistake?

http://cryptofresh.com/b/2062830

Let me know.  I was gonna try to spread some holiday cheer, but now I have to go to work. 

Merry Christmas

Pages: [1] 2 3