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.


Messages - checkrasier

Pages: 1 [2] 3
16
General Discussion / Re: BitShares 2 Release Coordination Thread
« on: October 16, 2015, 06:20:59 am »
Witness checkraiser has been updated and asking for your vote.

get_witness checkraiser
{
  "id": "1.6.44",
  "witness_account": "1.2.13774",
  "last_aslot": 0,
  "signing_key": "BTS8Jr9MQE61fZUa9tRvSYcFQRRr8j2baWouknxjRbPkpVtNACa9m",
  "vote_id": "1:55",
  "total_votes": 0,
  "url": "url-to-proposal",
  "total_missed": 0,
  "last_confirmed_block_num": 0

17
How does one get added to the approved delegate list?

My delegate is online and updated but I am under the impression you can't publish price feeds if your not in the top 101.




18
General Discussion / Re: Problem updating delegate to 0.4.22
« on: October 27, 2014, 07:05:19 pm »
Thanks

I'm running on an AWS instance so I will try to reboot and see if that fixes anything.

19
General Discussion / Problem updating delegate to 0.4.22
« on: October 27, 2014, 04:33:21 pm »
I am running into a problem updating my delegate to version 0.4.22 on ubuntu
The build seemed to complete with no problems.

Below is the error I am getting from gdb during re-indexing.

Re-indexing database... Approximately 65.39% complete.
Program received signal SIGBUS, Bus error.
[Switching to Thread 0x7fffe6302700 (LWP 4962)]
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:37
37      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory.

Any ideas what I am doing wrong? 

Should I try to redownload the blockchain?

Thanks

20
General Discussion / Re: Bter: bitUSD/USD price
« on: October 07, 2014, 06:01:33 pm »
It is very difficult to sell bitUSD in the market engine, there is very low demand. I think the solution to this issue will be the implementation of yield.
The yield is already implemented ... I have received some bitUSD (fractions) with my last transaction ..

So as I see it .. its a opportunity .. isn't it?

It seems to me offering interest on open BitUSD orders and drastically lowering the fee (say .01 BTSX) on cancelled orders would help to increase trading activity on the block chain. 
 

21
Stakeholder Proposals / If you like poker vote for delegate checkraiser
« on: October 04, 2014, 01:51:16 am »
Hello bitshares community, greetings from the windy city! 

I have learned so much from this great community since I began mining PTS in late 2013 and consider myself lucky to be part of the February snapshot.  The level of innovation being deliver by this platform is truly inspiring and has motivated me to setup a dedicated delegate on AWS (Oregon Based).  Delegate checkraiser is ready to server as a delegate and I have set the payrate to 50% as a way to give back to this great community.

Delegate checkraiser is updating with each release and now needs your vote to get into the top 100 to begin publishing price feeds.

wallet_approve_delegate checkraiser

With the other 50% my goal is to promote BitUSD (and other FIAT pegged assets) for use in online poker gaming. I can’t wait until someone launches a poker DAC!

My background is mechanical engineering and I have worked on the sales side of the software industry since the turn of the century. 

Please don’t hesitate to post questions and I will respond ASAP.

Thank you in advance for your vote!



btsx:checkraiser/approve

22
General Discussion / Re: Delegates Post Your Robot With your Name
« on: September 16, 2014, 08:11:39 pm »


checkrasier

23
Is there instruction on how to update and rebuild the linux client version as new releases come out?  I am guessing there is some way to get an update from github and then recomplie but any command help would be appreciated.
I will write one tomorrow .. it's pretty easy:

git pull; git submodule update;
cmake .
make


if you also want GUI:

make forebuildweb
make BitSharesX

Quote
How do I start publishing price feeds and client version information?
Is your delegate already vote up to the top 101 delegates? I am not sure if you can publish a price feed if not ..
the command is "wallet_publish_price_feed" ... stick a "help" in front and it will tell you what to do.

there is also a script that can help automate things:
https://github.com/Bitsuperlab/operation_tools/blob/master/btsxfeed/

Thanks for the help.  It was pretty easy to update once I figured out how to kill the screen session

How to kill screen session:

screen -ls

Find the PID running bitshares

screen -X -S [PID] kill


Update Bitsharesx:

cd bitsharesx
git pull
git  checkout v0.4.15-a
git submodule update
cmake .
make

Launch updated client:

cd ~/bitsharesx/programs/client
screen
gdb ./bitshares_client
>run
 

24
Update on this issue.  Since the margin order was still open I selected the cover option again. 
It appears that .0001 BitUSD was still owed for this transaction.  I paid required amount (and a second .1 BTSX transaction fee) at the BTSX collateral was returned.

Is there anyway to prevent this in the future? 

If I slightly over pay when covering a short will the system automatically return any possible over payment?

25
Excellent thanks for the info.

I am not yet voted into the top 101 as I just got the dedicated server up this weekend.

I will work on getting in the top 101 and then publish price feeds

26
So I setup a delegate this weekend on a linux VPS.  I am a novice at best on linux but the instruction were pretty straight forward so thank you to everyone making this process relatively straight forward.

Two question that I am sure have been answered previously but I have been unable to locate the related posts:

Is there instruction on how to update and rebuild the linux client version as new releases come out?  I am guessing there is some way to get an update from github and then recomplie but any command help would be appreciated.

How do I start publishing price feeds and client version information?



27
General Discussion / Covered a short position but margin order still open?
« on: September 15, 2014, 07:09:57 pm »
I recently covered an short position in the bitusd market.  The bitusd was subtracted from my wallet and the network paid the yield in that transaction.  My problem is the btsx collateral was not returned and the margin order is showing as open.

Using the win32 gui updated to 0.4.15a and re scanned the blockchain but still showing the margin order.

Any ideas on how to resolve this?

 

28
ok so I have some bitUSD all ready.
What do I need to do to collect the interest and how often is it calculated?

I want to know this too. I already have bitUSD and bitBTC which I bought well above the current btsx price. So I plan on holding on to them for the interest. Do we need to do anything to start gaining the returns on Wednesday, or do the returns only apply to people who acquire their bitAssets on Wednesday or later?

as i understand just put it in your account and don't place an order at the market.

@bytemaster
please consider to count bitUSD in market order for the yield as well. without that everyone will hord and not trade bitUSD.

Placing your bitUSD in market means you don't want to keep these bitUSD anymore, then why you still get interest? Interest encourages every hold bitUSD.

It means you are willing to buy or sell at a higher price than the current ask or bid.  Not having interest for funds that are part of market orders seems to discourage trading, hurt liquidity and the widen the spread. 

Am I missing something?

29
Thanks.

If there are no plans to support block production in the gui why do you give the user an option to register as a delegate in the GUI?

Is there another benefit to registering as a delegate other than block production potential?

30
When delegate block production is enabled any transaction sent appear as pending in the wallet (yet still goes through), and transactions sent to delegates or non delegate accounts in wallet don't show up at all. 

If I disable block production for all delegates and rescan block chain everything goes back to normal.

Is delegate block production not yet supported on windows?



Pages: 1 [2] 3