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.
@vikram (does paging work?)
you mean on site? Pagination ? Just to get it clear …
I just meant on this forum, does using '@member' notify the member.
By the way, there's a link on the faucet page which doesn't work for me. It's where it says:QuoteNeed help? Read How to Register a BitShares Account
My understanding is that after 17th June, names of 8 characters or more need to be registered via the faucet to avoid the prefix. Up to and including this date 8 character names will be fine, even if the faucet wasn't used.
I haven't seen this June 17th date, but let's assume that's correct, then it should go something like this ...
All 8 char names reg'd before June 8th will migrate as-is.
All 8 char names reg'd after June 8th up to 2.O will be prefixed at migration.
All 9+ char names reg'd anywhere before June 17th will migrate as-is.
All 9+ char names reg'd at the faucet after June 17th will migrate as-is.
All 9+ char names reg'd anywhere else after June 17th up to 2.O will be prefixed at migration.
Is that correct?
Great!
There's a typo in the title thoughQuoteHow heirarchical mutlisig works on #bitshares
Any chance we could get a link somewhere to the original "BitShares - A Peer To Peer Polymorphic Digital Asset Exchange" paper? I'd like to read it again, but the only link that I could find is a dead one: https://bitcointalk.org/index.php?topic=313873.0
Thanks!
Updated: https://bitshares.org/blog/2015/06/08/migrating-to-bitshares-2.0/#account-name-migration
IMHO, you should get rid of the "so that they can double as DNS names" part too. Maybe it ends up happening anyway, but don't commit to that. I think it will be a huge mistake personally. The economic model of paying a fixed fee determined by an algorithm and owning the name forever with no tax is flawed for domain names. You guys recognized this with the auction rules for the original BitShares DNS. A naming system with a different economic model will require a different namespace from account names (because it should still be possible to have account names with the fixed-fee true ownership model since their use case is different).
All nullstreet journal newsletter pdf links are broken, are they removed or have they been relocated... link?I've been updating my sites and have noticed that many previous links are still broken and have not been redirected like the DPOS related info. The docs dot bitshares subdomain is gone, if nothing else at least redirect the whitepapers to their new home as that is something many Internet sites have active links for.Bytemaster's Blog is MIA from the website? Probably done intentionally, it can still be found here http://bytemaster.github.io/ ... lots more broken links around the internet, maybe it would be good if things like this were redirected to their new home
yep good point..
https://bitshares.org/newsletter/2015/
but currently there is an issue with the 2014 archive .. guess due the fact the mailchimp archive snippet have problems to get executed via https.. will look into asap
The only reason I spent that BTS was to get the names as-is. Don't you think changing the rules and taking people's assets (in this case the names) goes against the entire spirit of a blockchain system?
Migrating the names with a prefix makes them useless to me.
Although I wouldn't be happy, I could understand a rule that *future* registrations would not keep the name. But to take away the ones I've already registered is really crappy.
Would you also take someone's BTS because it was sold to them at a cost too low for to support the network?
it's updated just fine
"Update: All account names registered on or after 2015-06-17 will be migrated if and only if they were registered using the BitShares Faucet."
Hello, I am the Name Narwhal. It is me who bought a bunch of BTS so that I could register a few accounts.
No, this is not a spam attack, and yes, I am actually interested in these names (and a bunch more). Every single name was chosen to meet "more than 8 characters, or contains no vowels or at least 1 number" - names where it's been announced that they will make it into the new genesis block. I actually spent a lot of time putting together the list of names I'd like (and then finding a way to get the bitshares client to support having more than a couple names).
I believe the BitShares system is the perfect base for a de-centralized DNS system. And I hope to contribute to that process - I have lots of experience with domain names and I'd like to support the community in making the BitShares namespace become more valuable. I'm clearly setting myself up to be interested in having that happen - I'm making an investment into BitShares.
The source for Graphene indicates that it may eventually become possible to use BitShares names as collateral. Think about it - if someone is running a business using a BitShares DNS name (or a future DNS-like system), that name is going to become valuable collateral. And if the system allows them to use it as collateral, the price of BitShares will start to become supported (indirectly) from assets outside of the BitShares system. I think that's extremely powerful and will be very good for BitShares community.
I have a way to - without overly bloating the blockchain - allow people to use their bitshares names for DNS and much more. And I look forward to discussing those ideas with all of you.
No, I don't intend to demand $2000 for the crappiest of names. In fact, for the next few days: if you had an account prior to June 8th, if there is name I have which you would like to own, let me know your name and I'll arrange to give you the private key of the name you want.
So, if the social consensus allows, I'm going to keep spending my BTS buying some more names I'd like to own when BitShares 2.0 is released.
NameNarwhal,
The protocol currently allows this, but the BTS 1.0 fees are too low for the cost to the network. We do not intend to revoke the accounts you have already registered. We are updating the migration rules to indicate that only names registered by the faucet will be migrated without a prefix.
