76
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.
77
General Discussion / Re: Referral program for bitshares.org and openledger.info domains
« on: November 03, 2015, 06:03:43 pm »
There was an issue with passing cookies via cross origin domain requests.
It's fixed now and you should be able to refer people to bitshares.org (root or any path inside) and your referrer will count for both bitshares.org/wallet and bitshares.openledger.info wallets.
It's fixed now and you should be able to refer people to bitshares.org (root or any path inside) and your referrer will count for both bitshares.org/wallet and bitshares.openledger.info wallets.
78
General Discussion / Re: Referral program for bitshares.org and openledger.info domains
« on: November 03, 2015, 01:00:14 pm »
This should work for bitshares.org domain and pass your referral to bitshares.org/wallet.
One of the reasons it didn't work for @tonyk might be a browser's cache - I've added a tracking code to bitshares.org not so long ago, so if page was cached it couldn't pass you referrals. The other possible reason could be related to issues passing cookies via CORS ajax requests in some browsers, will check this out..
One of the reasons it didn't work for @tonyk might be a browser's cache - I've added a tracking code to bitshares.org not so long ago, so if page was cached it couldn't pass you referrals. The other possible reason could be related to issues passing cookies via CORS ajax requests in some browsers, will check this out..
79
General Discussion / Re: Referral program for bitshares.org and openledger.info domains
« on: November 02, 2015, 11:28:21 pm »https://bitshares.openledger.info/?r=yourname#/create-account
will this link work?
If not, how should it be formatted?
Yes, this will work too.
80
General Discussion / Referral program for bitshares.org and openledger.info domains
« on: November 02, 2015, 10:55:41 pm »
First 2.0 referral program is up and running.
In order to participate you need to refer users to bitshares.org, openledger.info or bithsares.openledger.info domains and pass your account name (account needs to be a lifetime or annual member) via r= parameter.
You will collect either 60% (for lifetime referrer account) or 30% (annual member) of all fees paid by each user that registers by your link.
Example of a valid link:
In order to participate you need to refer users to bitshares.org, openledger.info or bithsares.openledger.info domains and pass your account name (account needs to be a lifetime or annual member) via r= parameter.
You will collect either 60% (for lifetime referrer account) or 30% (annual member) of all fees paid by each user that registers by your link.
Example of a valid link:
Code: [Select]
https://bitshares.org?r=youraccountname81
General Discussion / Re: [API] questions / suggestions for improvement
« on: November 02, 2015, 04:13:51 pm »Graphene API is just different, it's a paradigm shift - rather than "pulling" data from blockchain it exploits "push" concept allowing creation of close to real time clients.
It's pretty early in it's development, I expect it would be more user friendly as it mature and we implement more features and bindings. I predict the ideas we up to would have a big affect on all crypto APIs in the mid-term future.
Hey manBeen a long time.
So instead of reading the entire blockchain as an observer and picking our trigger events, the blockchain is alerting you pro-actively and you get to passively receive? That is very interesting, we had to build XChain to do that for us reliably with Counterparty and Bitcoin. If I understand what you're saying, we would not need to build that with Bitshares, it would talk directly to our vending machines or ecommerce system?
Hey Adam, yes been a long time
Correct, in Graphene the end clients can just subscribe to incoming transactions/balance changes events and update their state accordingly. Not sure what exactly XChain does - looks like its another function is to mirror the blockchain state into traditional database, in your architecture you still might need this layer, but it would definitely be easier to implement in Graphene and it would feel faster for end users.
82
General Discussion / Re: [API] questions / suggestions for improvement
« on: November 01, 2015, 03:13:29 pm »
Graphene API is just different, it's a paradigm shift - rather than "pulling" data from blockchain it exploits "push" concept allowing creation of close to real time clients.
It's pretty early in it's development, I expect it would be more user friendly as it mature and we implement more features and bindings. I predict the ideas we up to would have a big affect on all crypto APIs in the mid-term future.
It's pretty early in it's development, I expect it would be more user friendly as it mature and we implement more features and bindings. I predict the ideas we up to would have a big affect on all crypto APIs in the mid-term future.
83
Technical Support / Re: Where I can find in the interface version of webwallet?
« on: November 01, 2015, 02:41:36 pm »
It's on devs to do list to show version number in the gui.
Yes, a lot of open issues are duplicates, a lot wasn't closed after fixed, it would be nice if someone could go over the issues and closed duplicates and fixed ones.
Yes, a lot of open issues are duplicates, a lot wasn't closed after fixed, it would be nice if someone could go over the issues and closed duplicates and fixed ones.
84
Русский (Russian) / Re: Что я теряю пользуясь онлайн кошельком?
« on: October 30, 2015, 12:03:26 pm »Установка кошелька требует Виндовс 7 64 бит. У меня 32 бита. Я буду както ущемлен если буду хранить свои битшейрс в онлайн кошельке. (Т.е. без установки его на компьютер) ?
Нет, но это менее безопасно чем лайт кошелек, так как сейчас Вы скрипты получаете с сервера и если сайт взломают и подменят скрипты, то теоретически смогут «украсть» у Вас приватные ключи, а следственно и средства. Лайт версия хранит все скрипты у себя и не берет их с сервера.
Даже если веб-сервер взломают и подменят скрипты, то ключи так просто украсть не получится - они хранятся в браузере в зашифрованом виде и если в это момент вы не делаете транзакций, то вы в безопасности.
Кстати не забывайте делать бэкап, когда пользуетесь веб версией - если браузер очистит кэш, вы потеряете все ключи.
85
Technical Support / Re: Imported balances disappeared - non 2.0 account?
« on: October 29, 2015, 02:36:45 pm »I have a similar problem, i started 0.9.3c and tried to sync, but the client saying "not connected" so i exported the wallet as described and imported it
in the new 2.0 light client. But now i'm missing my last transactions, maybe because my client was not fully synced (i started the 0.9.3c client today,
last time was months ago) but how can i sync without a connection and additionally can i repeat the migration procedure when the 0.9.3c client is
synced to the last block before the hardfork?
You don't need 0.9.3c to be fully sync in order to move your keys to 2.0 - all your keys are already there, you don't get them over the network.
86
Русский (Russian) / Re: Откуда взялась первая монета Битшейрс
« on: October 29, 2015, 02:24:54 pm »Вот создали систему Битшейрс. И предположим я первый человек который захотел стать обладателем первой монеты BTS. Я взял свои доллары США и готов купить монету, но откуда она взялась у того кто мне ее продаст?
Её выдули из попы создатели bitshares. Так же как всякие стартапы содают акции, чтобы продать их на бирже и сколотить начальный капитал.
По сути вы правы - Bitshares это такая же компания, только децентрализованая (DAC) и BTS это акции компании, изначально все акции были распределены среди тех кто инвестировал в разработку Bitshares тем или иным способом.
87
General Discussion / Re: Graphene GUI testing and feedback
« on: October 27, 2015, 10:28:27 pm »market history is nice, but there's a decimal bug it seems, you can't use the exchanges at all now.
testing?
Fixed, thanks for testing.
88
General Discussion / Re: Core dev respond to GUI criticism
« on: October 27, 2015, 07:10:39 pm ».... Are you asking for something like "Convert" button? Such that you could specify a currency which you have, an asset which you want and the amount and the system would go ahead and buy that asset for you at a market price? Such button would be useful indeed."
I think this function would be very valuable for non-traders to use our system. Please consider this. Thank you
We are considering this:
When we were planning Graphene one of the features we wanted to have was "market orders" - user specifies only amount and buy or sell order executes at current market price. So in Graphene order can be executed in the same block it's placed and also it can be marked as "fill or kill" - this makes market orders much easier to implement. Now we only need to add simple buy/sell/short form to the GUI where user can specify amount, click Place button, agree with price and confirm.
89
Muse/SoundDAC / Re: MUSE Light client Release
« on: October 26, 2015, 09:15:39 pm »
Don't cybersquat the names - groups and artists won't use account names.
90
Technical Support / Re: Cant compile light_client
« on: October 24, 2015, 01:52:52 pm »
C++ light client is obsolete, please use node.js version, you need to build web wallet from this repo https://github.com/BitShares/bitshares-2-ui
after you built it via "npm run build" in web dir, you need to go to ../electron and type "npm run release", find light wallet in ./releases
Alternatively you can download light wallet from here https://github.com/bitshares/bitshares-2/releases
after you built it via "npm run build" in web dir, you need to go to ../electron and type "npm run release", find light wallet in ./releases
Alternatively you can download light wallet from here https://github.com/bitshares/bitshares-2/releases
