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 - fluxer555

Pages: 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 ... 50
121
General Discussion / Re: Bitshares price discussion
« on: May 06, 2017, 04:21:56 pm »
You lost me at

An increasingly ALT/Bitcoin bear market

This is the most bullish crypto market we've ever seen currently.

I think it's most obvious that the price rise is due to the good news that has come out: EOS + HERO

122
General Discussion / Re: The Hero from BitShares Island
« on: May 06, 2017, 12:17:20 am »
If I'm not mistaken, this is an idea you've been talking about for years, ever since market pegged assets came out. Your timing here seems to indicate that you're very bullish on BTS.

123
General Discussion / Re: BlockPay in Serious Trouble
« on: May 04, 2017, 08:44:05 pm »


They just want to make some money

Translation?

124
General Discussion / Re: Dan's Next Project - EOS Rears its Head
« on: May 04, 2017, 07:39:37 am »


That's some serious depth to break through.

125
General Discussion / Re: Dan's Next Project - EOS Rears its Head
« on: May 04, 2017, 01:49:34 am »
Stan just triple posted. I'm pretty sure that means something big is coming.

126
He complains about coins that are "forked" or "premined", but bitshares falls into that category. Let's not forget our bitshares history, folks!

We made up the term "sharedrop", but all it really is is a gentleman's premine.

No, it's not.  People complain that our chain isn't private enough.  Everytime a Bitshares user makes (or receives) a transaction, you can observe it.  This is a lot different than most coins where they just have a garbled hash for a wallet address.

Bitshares wallets are easily identifiable and thus, auditable when a sharedrop occurred.  There was no foul play with Bitshares.

However other coins, like the ones where the developer releases buggy code, the chain starts, and 90% of the people can't get it to run correctly allows the developer to get his hands on a sizeable number of coins fraudulently, and then release working code an hour or two later.  This has happened multiple times.  If I remember correctly Dash / Darkcoin started this way back in the early days if you can read the original Darkcoin launch threads that have not been edited.

And that was the whole point of Protoshares (PTS).  You had to mine them and that gave you rights to our first upgrade to BTSX.  Subsequent upgrades brought those mined shares up to ownership of BitShares 2.0. 
Then AngelShares (AGS) gave everyone a 100 day chance to smartmine - donate to fund work instead of fake work (burning electricity).  How innovative was that?

If you insist on calling all that a "premine" then every single chain that has ever upgraded with a single hard fork will have to be called a premine too. 

Sharedrops are just adopting a previously fair distribution across a different demographic than geeks with gnarly CPUs.

I agree with all this. I didn't mean to imply any negative connotations with "premine" as a word by itself. There are fair premines and unfair premines. I was attempting to differentiate its fairness by using the "gentleman" term :)

127
General Discussion / Re: Dan's Next Project - EOS Rears its Head
« on: May 03, 2017, 10:05:24 pm »
Perhaps the EOS UIA is the reason Stan has been accumulating BTS the last few months?!
You need to think BIGGER, Pinky!

Bitshares 3.0 on EOS chain?

128
If you're right about the market being swayed by incomplete information on CMC, congratulations! You now have an edge over the masses, and can profit from this knowledge if you know how to use it to your advantage.

129
I don't think it's CMC's job to be a judge of the currencies/assets. Their job is to report the current/historical price/volume/marketcap of cryptographic assets/currencies, and that's it. If you're using this as your sole resource for determining what you should invest in, you're the problem, not CMC.

To be clear, I am all in support for services or websites in addition to CMC that attempt to fairly make these kind of judgements.

130
Technical Support / Re: BitSharesX
« on: May 03, 2017, 03:57:25 pm »
Check the filesize of the wallet that failed to import, then check the filesize of the newly exported wallet. If they are different, then that means the content changed, and you should try re-importing it into the 2.0 wallet.

131
Technical Support / Re: BitSharesX
« on: May 03, 2017, 03:56:08 pm »
if you got "0" from recover accounts, that means there were no addition accounts recovered. That's ok. Run "wallet_regenerate_keys ACCOUNT-NAME 1000" (with ACCOUNT-NAME replaced with your account name), let it rescan again, and then try exporting the wallet.

I don't know why it would say it already exists. Sounds like it may be a bug. Make sure that you have permissions to write to where you want to save it (maybe need to run wallet as administrator as others have said).

132
General Discussion / Re: Dan's Next Project - EOS Rears its Head
« on: May 03, 2017, 03:41:08 pm »
EOS UIA  registered a month ago by sat0shi   

https://bitshares.org/wallet/#/asset/EOS

Interesting-

Quote
ENABLE MARKET FEE
REQUIRE HOLDERS TO BE WHITE-LISTED
ISSUER MAY TRANSFER ASSET BACK TO HIMSELF
ISSUER MUST APPROVE ALL TRANSFERS

133
Technical Support / Re: BitSharesX
« on: May 03, 2017, 03:03:05 pm »
Quote
"wallet_scan_progress": "3.51 %",

You'll have to wait now. You may have to wait after each step. It's what I did, find a book to read or some other activity, it took me about an hour each time :)

134
General Discussion / Re: Dan's Next Project - EOS Rears its Head
« on: May 03, 2017, 02:53:23 pm »
Do I smell a bitshares sharedrop? :D

135
Technical Support / Re: BitSharesX
« on: May 03, 2017, 02:20:04 pm »
You're basically there already. I don't know why the 2.0 wallet isn't importing your funds, and giving that TypeError.

My best guess right now would be to rescan your wallet in 0.9.3c, then re-export the keys, and try importing them again.

I found old documentation by using archive.org that helped me. Here is the info (converted to GitHub markdown):

https://gist.github.com/flux627/f16ad0daf02c3fe7fe58ce9d39b753ee

In my case, I had to do everything here except the last step (wallet_recover_transaction)

Pages: 1 2 3 4 5 6 7 8 [9] 10 11 12 13 14 15 16 ... 50