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

Pages: 1 ... 70 71 72 73 74 75 76 [77] 78 79 80 81 82
1141
General Discussion / Re: Testing BitShares XT Launch...
« on: May 03, 2014, 06:23:41 pm »
Quote from: xeroc on May 03, 2014, 05:14:41 pm
Are we sure that change-addresses are stored correctly in the database? if I send a tx to some addresses (generated with the utility "bts_create_key") and kill the terminal with CTRL+C .. restart the client again and type 'getbalance' it get a 0 in contrast to what I expect as change!? Maybe I made some mistake?

I believe the client does not usually automatically save after running rpc commands; someone seems to be looking at this: https://github.com/BitShares/bitshares_toolkit/pull/50

1142
KeyID / Re: Ethereum theorizing DNS
« on: April 26, 2014, 07:20:01 pm »
Quote from: toast on April 26, 2014, 05:07:38 pm
I've watched this whole thing before and I'm writing a response in the form of a blog post.
tl;dr I'm not worried =)

Link when post done!

1143
Technical Support / Re: How to learn the bitshares_toolkit framework quickly for a newbie?
« on: April 22, 2014, 10:30:28 pm »
How do you envision the codebase being organized to enable easily developing and maintaining multiple DACs per family? Specifically, I am considering whether it is feasible and desirable to separate BTS/DNS/P2P specific code into a BTS::DNS::P2P namespace which overrides the relevant stubs in BTS::DNS (additional DNS family members would then follow the same pattern).

1144
Technical Support / Re: How to learn the bitshares_toolkit framework quickly for a newbie?
« on: April 22, 2014, 03:57:49 am »
What do the FC_REFLECT* macros enable you to do in the rest of the fc library?

1145
Technical Support / Re: How to learn the bitshares_toolkit framework quickly for a newbie?
« on: April 18, 2014, 06:32:56 am »
Quote from: bytemaster on April 18, 2014, 05:10:58 am
Quote from: John-S on April 18, 2014, 02:36:27 am
I'm a noob myself, but have learned a lot in the past couple of days.  Message me with your specific questions and I'll see what I can't do to help bootstrap you along.

- John "S"

Post questions here and I can double check understanding and future devs can see the questions/answers as well.

  • What is the purpose of separating some of the class functionality into the *_impl inner classes (e.g. bts::wallet::detail::wallet_impl)?
  • What exactly does the asset class now represent? Won't we run into precision issues now that it is 64 bits again (rather than 128)?

1146
KeyID / Re: rebranding update
« on: April 16, 2014, 06:05:23 pm »
Quote from: toast on April 16, 2014, 12:40:56 am
I was thinking more like:

BitShares DNS: Decentralized Namespace Services

DNS/P2P
DNS/KEY
DNS/DAC

"Nameshares" are shares of DNS DACs, and can also be used in place of the more verbose "bitshares DNS". More specific than "bitshares" but less specific than "P2Pshares".
Quote from: toast on April 16, 2014, 12:41:51 am
This solution has the problem that traditional DNS means domains only while our DNS is all namespaces - I think this tradeoff is ok because it makes all our other stuff fit together so much more cleanly

Hmm I think I might like this. In what contexts do you see NameShares (or is it Nameshares) being used vs. BitShares DNS?

What do people think about the overloading of the DNS acronym?

1147
KeyID / Re: rebranding update
« on: April 15, 2014, 10:03:02 pm »
Quote from: unlimited_power on April 15, 2014, 09:39:09 pm
Quote from: toast on April 14, 2014, 09:18:26 pm
Quote from: luckybit on April 14, 2014, 03:50:17 am
Quote from: toast on April 02, 2014, 05:03:30 pm
Making a thread specifically for feedback on last status update:

Quote
BitShares DNS is the name of the namespace DAC family, and *maybe* the name of a a possible proto-DAC for this family. If there is a proto-dac then new DACs can use burn rounds (among other options) for snapshots, if there is no proto-DAC then new chains will do burn rounds / snapshots from previous chains or PTS/AGS or both.

What used to be called "BitShares DNS" is now simply called ".p2p" - that is the name of both the blockchain and the TLD, with ".P2P" as a ticker. This will not be heavily branded with BitShares but rather will set an example of how a project can benefit from participating in the bitshares ecosystem.

Can we rename Bitshares DNS into Nameshares?

Nameshares just sounds better. Just like Namecoin/Bitcoin. Since it really has little to do with Bitshares itself, Nameshares just is simple enough to catch on.

I have thought about this in depth and concluded that the cost of pissing off all the namecoiners is totally worth it

 +5%

I am starting to see a pattern:
  • DomainShares: A single company providing a decentralized domain name mapping service
  • BitShares Domains/BitShares DNS: A family of companies providing decentralized domain name mapping services
  • NameShares: A family of companies providing decentralized name mapping services
Why not skip to the end:

BitShares Lookup/Bitshares Map/BitShares Dictionary: A family of companies providing decentralized (key, value) mapping services (see: https://en.wikipedia.org/wiki/Associative_array)

Family Members:
  • BTS/MAP/P2P: Map domain names (with .p2p TLD) to IP addresses, SSL keys, etc. (similar to Namecoin's d/ prefix)
  • BTS/MAP/KEY: Map personal names to PGP public keys, Keyhotee IDs, etc. (similar to Namecoin's id/ prefix)
  • BTS/MAP/DAC: Map exchange ticker symbols to particular blockchains, etc.
And so on... Thoughts on this kind of generalization? Edit: I suppose the difference is subtle but at least in my head mapping keys to values seems to be more general than mapping names.

Actually I guess Namecoin exactly bills itself as a "decentralized key/value registration and transfer system" (see: http://namecoin.info/). This Name metaphor is throwing me off though, as keys can be more than just names.

1148
KeyID / Re: rebranding update
« on: April 15, 2014, 09:39:09 pm »
Quote from: toast on April 14, 2014, 09:18:26 pm
Quote from: luckybit on April 14, 2014, 03:50:17 am
Quote from: toast on April 02, 2014, 05:03:30 pm
Making a thread specifically for feedback on last status update:

Quote
BitShares DNS is the name of the namespace DAC family, and *maybe* the name of a a possible proto-DAC for this family. If there is a proto-dac then new DACs can use burn rounds (among other options) for snapshots, if there is no proto-DAC then new chains will do burn rounds / snapshots from previous chains or PTS/AGS or both.

What used to be called "BitShares DNS" is now simply called ".p2p" - that is the name of both the blockchain and the TLD, with ".P2P" as a ticker. This will not be heavily branded with BitShares but rather will set an example of how a project can benefit from participating in the bitshares ecosystem.

Can we rename Bitshares DNS into Nameshares?

Nameshares just sounds better. Just like Namecoin/Bitcoin. Since it really has little to do with Bitshares itself, Nameshares just is simple enough to catch on.

I have thought about this in depth and concluded that the cost of pissing off all the namecoiners is totally worth it

 +5%

I am starting to see a pattern:
  • DomainShares: A single company providing a decentralized domain name mapping service
  • BitShares Domains/BitShares DNS: A family of companies providing decentralized domain name mapping services
  • NameShares: A family of companies providing decentralized name mapping services
Why not skip to the end:

BitShares Lookup/Bitshares Map/BitShares Dictionary: A family of companies providing decentralized (key, value) mapping services (see: https://en.wikipedia.org/wiki/Associative_array)

Family Members:
  • BTS/MAP/P2P: Map domain names (with .p2p TLD) to IP addresses, SSL keys, etc. (similar to Namecoin's d/ prefix)
  • BTS/MAP/KEY: Map personal names to PGP public keys, Keyhotee IDs, etc. (similar to Namecoin's id/ prefix)
  • BTS/MAP/DAC: Map exchange ticker symbols to particular blockchains, etc.
And so on... Thoughts on this kind of generalization? Edit: I suppose the difference is subtle but at least in my head mapping keys to values seems to be more general than mapping names.

1149
General Discussion / Re: Our new website is now LIVE!
« on: April 15, 2014, 06:09:04 am »
Quote from: bytemaster on April 15, 2014, 02:36:30 am
Quote from: unlimited_power on April 14, 2014, 07:47:43 pm
Quote from: toast on April 14, 2014, 05:32:03 pm
We have no official wiki. Dan wants to put everything on bitshares.org, I'm putting stuff for dns in my auto github wiki.

So maybe one of these?
https://github.com/BitShares/bitshares.org/wiki
https://github.com/BitShares/bitshares_toolkit/wiki

When if/everything is consolidated into an official wiki, someone should make sure any useful information from here is also transferred: http://wiki.invictus.io/en/Main_Page

Github + bitshares.org are the only two websites I want information on.   I am all for using the github wiki.

I think everything should be copied off (careful not to miss anything) of http://invictus-innovations.com/ and http://invictus.io/ and organized into bitshares.org + GitHub wiki(s). Then those sites should be replaced with automatic redirects to bitshares.org.

1150
General Discussion / Re: Delegated Proof of Stake (DPOS) White Paper
« on: April 15, 2014, 05:52:05 am »
Quote from: bytemaster on April 15, 2014, 02:16:16 am
I have been putting together more detailed algorithm documentation here:

http://bitshares.org/documentation/group__dpos.html

If you see anything that needs correction or clarification let me know... the webpage is generated from the following doxygen file:

https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/blockchain/dpos.dox

My questions:

Quote
At all times every share is either voting for or against some delegate but not both.
Are shares already voting at genesis?

Quote
Every transaction moves a vote from one delegate to either the same delegate or another delegate.
Just a single vote or proportional to stake of transaction inputs? If the latter, then proportional to CDD, input BIPS, or what?

Quote
All delegates must register a unique identifier, that can be used to vote for or against them [...] delegates are registered using the bts::blockchain::claim_name_output class
How is the chain bootstrapped i.e. how are the first blocks created so that prospective delegates can register identifiers? What is the minimum number of delegates needed for the chain to operate?

Quote
When registering an identifier a signup fee equal to 100 times the average revenue per block must be paid. This will insure that a delegate must produce at least 1000 blocks to break even and discourage people from running for the delegate position that are not serious.
So a delegate receives 10% of the transaction fees for a block it signs, while the remaining 90% become company dividends?

Quote
Voting Algorithm [...] Delegate Scoring [...]
Is this simply the particular voting and ranking strategy that will be used by the reference wallet implementation?

1151
General Discussion / Re: Delegate ring signature for reporting collusion
« on: April 14, 2014, 07:47:43 pm »
Quote from: toast on April 14, 2014, 05:32:03 pm
We have no official wiki. Dan wants to put everything on bitshares.org, I'm putting stuff for dns in my auto github wiki.

So maybe one of these?
https://github.com/BitShares/bitshares.org/wiki
https://github.com/BitShares/bitshares_toolkit/wiki

When if/everything is consolidated into an official wiki, someone should make sure any useful information from here is also transferred: http://wiki.invictus.io/en/Main_Page

1152
General Discussion / Re: BTS-->BTS X-->BTS ME-->BTS YOU-->BTS HIM-->?
« on: April 06, 2014, 07:15:39 pm »
Quote from: jabbajabba on April 06, 2014, 09:04:36 am
Quote from: fuznuts on April 06, 2014, 07:37:06 am
Quote from: unlimited_power on March 28, 2014, 07:44:26 pm
Don't forget -->BTS Xe to make the feminists happy..

https://github.com/Feminist-Software-Foundation/Internet-plus-Equality

Jeez...I can tell ive been too focused on one portion of the forums lately.  This made me laugh so hard I teared up..
The Feminine

    Bitch = Strong Womxn
    Woman = Empowered female
    Cunt = Pretty pink princess
    Pussy = Assets

It's time for BitPussy

Well, I suppose I'll be going long.

1153
General Discussion / Re: Delegated Proof of Stake (DPOS) White Paper
« on: April 06, 2014, 06:04:25 pm »
This is awesome. Dan, please update the whitepaper to reflect the updates when you get the time, so that we can continue to publicize it.

1154
KeyID / Thin Clients
« on: April 05, 2014, 01:16:29 pm »
Are there any Namecoin thin clients that use SPV or something? I would imagine we will eventually want such a thing.

https://en.bitcoin.it/wiki/Thin_Client_Security

1155
KeyID / SyncNet
« on: April 05, 2014, 12:33:42 pm »
https://github.com/jminardi/syncnet
http://jack.minardi.org/software/syncnet-a-decentralized-web-browser/

Found this project on this HN post about Namecoin: https://news.ycombinator.com/item?id=7532349

We should get him to use one of our DNS chains rather than Colored Coins/Namecoin.

Pages: 1 ... 70 71 72 73 74 75 76 [77] 78 79 80 81 82

Page created in 0.201 seconds with 23 queries.