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

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 ... 64
151
General Discussion / Re: Curiosumé + Bitshares = Intrinsic Coin
« on: September 09, 2015, 01:49:59 am »
Hey all ... newbie here.

We need help on some ideas that we are working on at The Ingenesist Project.  I've been on the Beyond Bitcoin Hangout for the last several months learning about this community.  I believe that here is great potential here.  Is this the right place to ask for interaction with this members of this group?  Let me know and hopefully we can start a thread.  Thank you very much.

Welcome!

I'll just come right out and say Curiosume puzzles me.  Cross-posting from here: https://bitsharestalk.org/index.php/topic,18214.msg232723.html#msg232723

Quote
All money is backed by the productivity of those who choose to use it; that's just how network effect works.  The more people there are who consider the currency valuable and who are willing and able to provide a variety of goods and services in exchange for it, the greater the utility of that currency.

I could be misunderstanding, but my initial impression was that Curiosume is an attempt to create a currency based on these principles without recognizing that this is already a big part of how every other currency works.

Just being honest here with no intention of being mean-spirited or overly critical.  I really don't understand how Curiosume is different from any other currency except that it's catering to engineers first as high value members of the global economy.  Hopefully you can tell me what I'm missing.

152
General Discussion / Re: I'm going to make all of you rich
« on: September 05, 2015, 05:31:34 am »
The messaging and filesharing system should absolutely be done off chain, but using chain registered account names for lookups.  Something like this, but with BitShares account keys instead of PGP:

http://retroshare.sourceforge.net/

This uses distributed hash tables for IP lookups from a public key, so no central server is necessary, but it isn't healthy for battery life on mobile devices to maintain a full DHT node.  Because of this, I recommend a mobile client that establishes a single direct connection by DHT to a full node that acts as a proxy for all other connections.

The referral system is actually reasonable, I think.  It's much less spammy since there's no reward unless those referred actually end up using the service and paying fees.

153
General Discussion / Re: Curiosume money theory
« on: August 30, 2015, 12:57:17 pm »
All money is backed by the productivity of those who choose to use it; that's just how network effect works.  The more people there are who consider the currency valuable and who are willing and able to provide a variety of goods and services in exchange for it, the greater the utility of that currency.

I could be misunderstanding, but my initial impression was that Curiosume is an attempt to create a currency based on these principles without recognizing that this is already a big part of how every other currency works.

154
General Discussion / Re: Decoupling bitAssets from BTS through POW
« on: August 28, 2015, 01:02:22 pm »
This is wildly out there in terms of ideas and bare with me and a lot of controversial statements follow, but hear me out:

1) POW is the direct conversion of electricity (kWh) into tokens
2) Using BTS as the collateral for bitAssets can lead to a self reinforcing collapse since they two things are intrinsicly linked
3) The price of electricity is relatively stable compared to crypto currencies

Given these assumptions, is it possible to create a kWh token, created by burning N kilowatt-hours through POW, and then to use that token as the collateral backing bitAssets?

In order for an asset to be backed, the collateral backing the asset must be retrievable.  A token cannot be backed by POW as collateral because the electricity cannot be retrieved, its network can only be secured by POW as a recurring cost.

155
General Discussion / Re: Test Net for Advanced Users
« on: August 25, 2015, 12:18:09 pm »
In the interest of not slipping the release date we are going to fall back to 3 or 5 second blocks using the current P2P code.   Then after we update the P2P code we can increase the block rate to 2 and ultimately 1 second block times.

Ben is in the process of preparing instructions for committee members on how to change the block interval and we plan to dynamically update the test network to prove that we can do this on a live network.

Excellent.  As my martial arts instructor always says: "train the correct movement, and speed will come easily later."

156
General Discussion / Re: Please stop changing the rules of the game
« on: August 24, 2015, 12:52:40 pm »
Please try to make just one damn thing work (commercially speaking) before screwing it off to go and make something else.

You don't like how things are going. This is why we have Voting.

Indeed.  Which is why top priority should be getting BitShares to the point at which it is independent with an effective and user friendly voting system to generate consensus on how it needs to adapt.  Bytemaster has indicated that he's all in favor of BitShares outgrowing its dependence on him, so it just remains to see whether he follows through on that.  If he does, I think it may become unstoppable, but if he cripples it with IP/licensing nonsense then who knows.

BM has literally said "if we vote on X then they won't vote right"...

I must have missed that, but that sort of inconsistency would be another good reason to prioritize independence from his (and any other individual's) authority.  I have a lot of respect for BM for how far he's gotten this project, but way too many people around here have been treating him like a god for way too long, and I don't think that's been healthy for him.  He's way better at R&D than he is at leadership and follow through.

157
General Discussion / Re: Test Net for Advanced Users
« on: August 22, 2015, 02:27:46 am »
Under the new protocol transactions only get sent once (vs twice under the current protocol) so bandwidth should be lower and block latencies will be lower because we do not send transaction data with the blocks like we do today.

So assuming 250ms ping times (125ms one way), the new system should support forkless operation with witnesses up to 6 hops apart as long as block production time + ((block validation time + block transmission time) * 6) all add up to less than 250ms.  At 4 hops of separation between witnesses that allows 500ms for block production time + ((block validation time + block transmission time) * 4).  Does this sound right?

Is one second block time just because it sounds good and it's a challenging goal, or would moving to 2 second intervals be significantly detrimental to some particular use case?  1 second seems doable, just wondering.

158
General Discussion / Re: Please stop changing the rules of the game
« on: August 22, 2015, 01:59:39 am »
Without change that results from innovation, Bitshares would already be worthless. It is revolutionary experimental software on the bleeding edge of network technology.  Honestly, what do you expect?

The constant fretting about sharesdrops and 'value proposition' is pretty ugly. Developers must do what is best for their project. Anyone can create an asset in Bitshares.  Bitshares has enormous potential value irrespective of a future gift.

Indeed.  Sharedrops are not a real factor in my continuing to hold BTS.  Sharedrops will buy my attention though; when I'm seriously sharedropped on I will take the time to see if I think the new project deserves my support.  That's the point of sharedrops.

159
General Discussion / Re: Please stop changing the rules of the game
« on: August 22, 2015, 01:09:33 am »
Please try to make just one damn thing work (commercially speaking) before screwing it off to go and make something else.

You don't like how things are going. This is why we have Voting.

Indeed.  Which is why top priority should be getting BitShares to the point at which it is independent with an effective and user friendly voting system to generate consensus on how it needs to adapt.  Bytemaster has indicated that he's all in favor of BitShares outgrowing its dependence on him, so it just remains to see whether he follows through on that.  If he does, I think it may become unstoppable, but if he cripples it with IP/licensing nonsense then who knows.

160
General Discussion / Re: Test Net for Advanced Users
« on: August 21, 2015, 12:51:22 pm »
Restarted my node and seem to be back on chain:

Code: [Select]
get_dynamic_global_properties
{
  "id": "2.1.0",
  "random": "35ece2ef7aac03b97de7c75e54830f57d2c8100c",
  "head_block_number": 64591,
  "head_block_id": "0000fc4f697a5655e44786cfea52ab4c6025ea86",
  "time": "2015-08-21T12:46:15",
  "current_witness": "1.6.85",
  "next_maintenance_time": "2015-08-21T12:50:00",
  "witness_budget": 51808059,
  "accounts_registered_this_interval": 0,
  "recently_missed_count": 0,
  "dynamic_flags": 0
}

Seems like the main issue I'm having is that I'm not getting enough connections.  If every node is only getting one or two connections, and running lower performance servers, it could be forking from latency issues.  How many connections are other people getting?

161
General Discussion / Re: Test Net for Advanced Users
« on: August 21, 2015, 12:40:26 pm »
Looks like my node fell off the chain over the night, probably because I never got more than one peer connection consistently.

Code: [Select]
get_dynamic_global_properties
{
  "id": "2.1.0",
  "random": "e96759cb979ef4620404d4a116c64d4e6b9bd0e8",
  "head_block_number": 43793,
  "head_block_id": "0000ab110f83c3641467c59ae7daec0c26e9537d",
  "time": "2015-08-21T06:35:29",
  "current_witness": "1.6.72",
  "next_maintenance_time": "2015-08-21T06:40:00",
  "witness_budget": 95817007,
  "accounts_registered_this_interval": 0,
  "recently_missed_count": 0,
  "dynamic_flags": 0
}

Code: [Select]
2344668ms p2p        node.cpp:4404                 dump_node_status     ] ----------------- PEER STATUS UPDATE --------------------
2344668ms p2p        node.cpp:4407                 dump_node_status     ]  number of peers: 1 active, 0, 0 closing.  attempting to maintain 20 - 200 peers
2344668ms p2p        node.cpp:4412                 dump_node_status     ]        active peer 45.55.6.216:1776 peer_is_in_sync_with_us:true we_are_in_sync_with_peer:true
2344668ms p2p        node.cpp:4425                 dump_node_status     ] --------- MEMORY USAGE ------------
2344668ms p2p        node.cpp:4426                 dump_node_status     ] node._active_sync_requests size: 0
2344669ms p2p        node.cpp:4427                 dump_node_status     ] node._received_sync_items size: 3588
2344669ms p2p        node.cpp:4428                 dump_node_status     ] node._new_received_sync_items size: 0
2344669ms p2p        node.cpp:4429                 dump_node_status     ] node._items_to_fetch size: 0
2344669ms p2p        node.cpp:4430                 dump_node_status     ] node._new_inventory size: 0
2344669ms p2p        node.cpp:4431                 dump_node_status     ] node._message_cache size: 2
2344669ms p2p        node.cpp:4434                 dump_node_status     ]   peer 45.55.6.216:1776
2344669ms p2p        node.cpp:4435                 dump_node_status     ]     peer.ids_of_items_to_get size: 0
2344669ms p2p        node.cpp:4436                 dump_node_status     ]     peer.inventory_peer_advertised_to_us size: 5
2344670ms p2p        node.cpp:4437                 dump_node_status     ]     peer.inventory_advertised_to_peer size: 104
2344670ms p2p        node.cpp:4438                 dump_node_status     ]     peer.items_requested_from_peer size: 0
2344670ms p2p        node.cpp:4439                 dump_node_status     ]     peer.sync_items_requested_from_peer size: 0
2344670ms p2p        node.cpp:4441                 dump_node_status     ] --------- END MEMORY USAGE ------------
2345990ms p2p        node.cpp:1340                 terminate_inactive_c ] Sending a keepalive message to peer 45.55.6.216:1776 who hasn't sent us any messages in the last 37 seconds

162
General Discussion / Re: Test GUI for Normal Users!
« on: August 21, 2015, 04:12:24 am »
How do I clear a previous wallet from my browser?  I have a previous wallet with a different chain id

Depends on OS/browser.  On Linux/Firefox you can delete the files in:

Code: [Select]
/home/[yourusernamehere]/.mozilla/firefox/[randomlygeneratedprofilenamehere].default/storage/default/https+++graphene.bitshares.org/
Obviously be careful doing things like this if you actually use a web wallet to store anything of real value.  Don't lose your private keys.

163
General Discussion / Re: Test Net for Advanced Users
« on: August 21, 2015, 04:04:03 am »

Did the chain ID change or am I on a fork?

test5 is a brand new data directory.

Code: [Select]
./witness_node -d test5 genesis-json /home/james/Downloads/aug-20-test-genesis.json --resync-blockchain --witness-id '"1.6.5250"' --private-key '["GPH7kNZtp64ZR1R4yC2w9bDLFNHkM8L2AFZSj1E", "5Jnwg...JC7Ur"]' -s "104.236.51.238:1776"

Code: [Select]
3270744ms th_a       thread.cpp:95                 thread               ] name:p2p tid:139985686546176
3270851ms ntp        ntp.cpp:81                    request_now          ] sending request to 198.60.22.240:123
3270851ms th_a       application.cpp:117           reset_p2p_node       ] Adding seed node 104.236.51.238:1776
3270853ms th_a       application.cpp:129           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:59551
3270854ms th_a       witness.cpp:107               plugin_startup       ] WARNING: Unable to find witness 1.6.5250. Postponing initialization until syncing finishes.
3270854ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
3270854ms th_a       main.cpp:166                  main                 ] Chain ID is b6ff5d956ca601b3682edbc52c5678819a63dd80f5c0fad00a289d1a09c4662e
3270928ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 198.60.22.240:123
3270928ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: -7351300, round_trip_delay 77122
3270929ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -7351300

Chain ID should be "d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083".  Try this node as seed: 176.221.43.130:33323

164
General Discussion / Re: Test Net for Advanced Users
« on: August 21, 2015, 03:23:27 am »
Here are the available logging levels: all debug info warn error off

Not sure why I'm not getting any more peers:

Code: [Select]
1503270ms p2p        node.cpp:4404                 dump_node_status     ] ----------------- PEER STATUS UPDATE --------------------
1503270ms p2p        node.cpp:4407                 dump_node_status     ]  number of peers: 1 active, 0, 0 closing.  attempting to maintain 20 - 200 peers
1503271ms p2p        node.cpp:4412                 dump_node_status     ]        active peer 176.221.43.130:33323 peer_is_in_sync_with_us:true we_are_in_sync_with_peer:true
1503271ms p2p        node.cpp:4425                 dump_node_status     ] --------- MEMORY USAGE ------------
1503271ms p2p        node.cpp:4426                 dump_node_status     ] node._active_sync_requests size: 0
1503271ms p2p        node.cpp:4427                 dump_node_status     ] node._received_sync_items size: 0
1503271ms p2p        node.cpp:4428                 dump_node_status     ] node._new_received_sync_items size: 0
1503271ms p2p        node.cpp:4429                 dump_node_status     ] node._items_to_fetch size: 0
1503271ms p2p        node.cpp:4430                 dump_node_status     ] node._new_inventory size: 0
1503271ms p2p        node.cpp:4431                 dump_node_status     ] node._message_cache size: 2
1503271ms p2p        node.cpp:4434                 dump_node_status     ]   peer 176.221.43.130:33323
1503272ms p2p        node.cpp:4435                 dump_node_status     ]     peer.ids_of_items_to_get size: 0
1503272ms p2p        node.cpp:4436                 dump_node_status     ]     peer.inventory_peer_advertised_to_us size: 117
1503272ms p2p        node.cpp:4437                 dump_node_status     ]     peer.inventory_advertised_to_peer size: 0
1503272ms p2p        node.cpp:4438                 dump_node_status     ]     peer.items_requested_from_peer size: 0
1503272ms p2p        node.cpp:4439                 dump_node_status     ]     peer.sync_items_requested_from_peer size: 0
1503272ms p2p        node.cpp:4441                 dump_node_status     ] --------- END MEMORY USAGE ------------

165
General Discussion / Re: Test Net for Advanced Users
« on: August 21, 2015, 03:11:02 am »
Thanks.  I am running with the new logging now.

Interestingly enough those changes prevent anything from showing up in the terminal

Yeah, you can change it so it shows up both places, just define whichever appenders you want, and then direct each logger to one or more of them.  Here's what mine looks like now:

Code: [Select]
# declare an appender named "stderr" that writes messages to the console
[log.console_appender.stderr]
stream=std_error

# declare an appender named "p2p" that writes messages to p2p.log
[log.file_appender.p2p]
filename=logs/p2p/p2p.log
# filename can be absolute or relative to this config file

# route any messages logged to the default logger to the "stderr" logger we
# declared above, if they are info level are higher
[logger.default]
level=info
appenders=stderr

# route messages sent to the "p2p" logger to the p2p appender declared above
[logger.p2p]
level=debug
appenders=p2p,stderr

We need to find what all other loggers are in use and at what levels...

Pages: 1 ... 4 5 6 7 8 9 10 [11] 12 13 14 15 16 17 18 ... 64