Many thanks guys - that was indeed the solution :)
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.
Show posts Menu{"id":1,"method":"call","params":[0,"get_block",[4658091]]}
{code:1,message:7 bad_cast_exception: Bad Cast
Invalid cast from object_type to Array
{"type":"object_type"}
th_a variant.cpp:530 get_array,data:{code:7,name:bad_cast_exception,message:Bad Cast,stack:[{context:{level:error,file:variant.cpp,line:53
0,method:get_array,hostname:,thread_name:th_a,timestamp:2016-04-09T20:28:59},format:Invalid cast from ${type} to Array,data:{type:object_type}}
]}}
Quote from: xeroc on March 30, 2016, 10:10:06 AM
I assume you mean the mid-price of the last 24h candle? .. mid price as in high-low?
Quote from: xeroc on March 29, 2016, 08:18:30 AM
I can write a bot for this that sets the CER at last_trade +5% or so .. or use the 24h average instead of last_trade.
What do you think makes most sense?
Quote from: xeroc on March 20, 2016, 10:08:22 AM
Build in 'Release' mode instead.
Anyway, this bug should be fixed
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make
[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
In file included from /home/coinbox/bitshares-2/libraries/chain/database.cpp:30:0:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp: In member function âvoid graphene::chain::database::update_worker_votes()â:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp:105:53: error: âHARDFORK_607_TIMEâ was not declared in this scope
bool allow_negative_votes = (head_block_time() < HARDFORK_607_TIME);
Quote from: tonyk on March 11, 2016, 09:39:55 PM
OP-er. Wrong!
Quote from: xeroc on March 08, 2016, 09:05:57 AM
Most of the committee seems to be fine with reducing issuer/burn fees out of schedule to support our existing business partners. We are evaluating out options
Quote from: Bhuz on March 07, 2016, 06:28:53 PM
Anyway, we are already discussing about it, and I personally hope we would be able to push this change asap.
I personally like more the on-demand issue/burn scheme than the pre-issue one.
Quote from: xeroc on March 07, 2016, 11:19:07 AM
The Committee will take your valuable input into considerations. I've added a remark to our current fee schedule:
https://github.com/BitShares-Committee/Instructions/commit/dd23653e17b24ee5a1e6c8a25378022b9f9c2eba
@monsterer .. In the meantime, what would be the argument of having a next-to-burn account that collects some of those assets and burns them after a couple of weeks to spare fees?
In the end, if they are held by the issue, your customers can have the same kind of trust that put into you not just issuing new shares. All they need to do is take another balance into consideration to verify that the supply matches the debt, not?
Quote from: abit on March 07, 2016, 10:38:35 AM
Good point.
Afaik OpenLedger is operating in a pre-issue schema, BlockTrades operates TRADE.BTC in a pre-issue schema as well but on-demand-issue schema for DOGE/DASH.
Page created in 0.150 seconds with 13 queries.