http://mobile.reuters.com/article/idUSKCN0WX2YF

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
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
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: faucet@example.com
  exception_recipients: admin@example.com

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.

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.

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.

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)


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.

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.

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.