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 - 8bit

Pages: [1] 2 3 4
1
Is your wallet unlocked? Perhaps the command you are trying requires the wallet to be unlocked.

Yes, I keep my wallet unlocked because I run delegates. And I'm only trying to grab blockcount and blockchain config. Not sure if it requires the wallet to be open, but either way, it is.

Thanks for the thought, though

Quote
   "rpc_endpoint": "0.0.0.0:0",
    "httpd_endpoint": "0.0.0.0:0",
    "htdocs": "./htdocs"

tried that, and still getting the same error... do you have anything located in your wallet's ./htdocs folder? Is that where you put your python stuff?

2

path: '/',
->
path: '/rpc',

Thanks for the response, toast. Am I doing this right?:

wallet config:

Code: [Select]
  "rpc": {
    "enable": true,
    "rpc_user": "test",
    "rpc_password": "test",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "path": "/"
  },

node.js config:

Code: [Select]

DELBID.rpc = require('node-json-rpc');
DELBID.rpc.options = {
port: 9989,
host: '127.0.0.1',
path: '/rpc',
strict: true,
login: "test",
hash: "test"
};

DELBID.rpc.client = new DELBID.rpc.Client(DELBID.rpc.options);
DELBID.rpc.client.call({"jsonrpc": "2.0", "method": "blockchain_get_config", "params": []}, function(err, res) {
if (err) { console.log(err); } else {
console.log(res);
}
});

I'm still getting a 400 error...

Haven't tried in Node JS, however here is the code I used to connect via Python:

https://bitsharestalk.org/index.php?topic=4125.msg84087#msg84087

Thanks! Would you mind posting the rpc section of your wallet config as well?

3
Happypatty, are you using RPC to pull data from the blockchain? Could I look at your code? I'm having trouble connecting.

See here: https://bitsharestalk.org/index.php?topic=6270.0

4
I'm trying to get the BTSX client to talk to a node.js app using RPC. The client starts the RPC server fine:

Code: [Select]
$ ./bitshares_client --server --httpport 9989
Loading blockchain from "/home/eightbit/.BitSharesX/chain"
Loading config "/home/eightbit/.BitSharesX/config.json"
Starting JSON RPC server on port 50022 (localhost only)
Starting HTTP JSON RPC server on port 9989 (localhost only)

But when I try to run my node.js server, I get:

Quote
Client: TODO Status Code: 400

Which refers to:

Quote from: wikipedia
4xx Client Error
The 4xx class of status code is intended for cases in which the client seems to have errored. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user.

400 Bad Request
The request cannot be fulfilled due to bad syntax.

Here is the RPC section of my config.json:

Code: [Select]
  "rpc": {
    "enable": true,
    "rpc_user": "test",
    "rpc_password": "test",
    "rpc_endpoint": "127.0.0.1:0",
    "httpd_endpoint": "127.0.0.1:0",
    "htdocs": "/"
  },

and here is the code I'm using in node:

Code: [Select]
DELBID.rpc = require('node-json-rpc');

DELBID.rpc.options = {
// int port of rpc server, default 5080 for http or 5433 for https
port: 9989,
// string domain name or ip of rpc server, default '127.0.0.1'
host: '127.0.0.1',
//username
login: "test",
//password
hash: "test"
// string with default path, default '/'
path: '/',
// boolean false to turn rpc checks off, default true
strict: true,
};

// Create a server object with options
DELBID.rpc.client = new DELBID.rpc.Client(DELBID.rpc.options);

//run blockchain_get_config in the wallet and print the results to the console
DELBID.rpc.client.call({"jsonrpc": "2.0", "method": "blockchain_get_config", "params": []}, function(err, res) {
if (err) { console.log(err); } else {
console.log(res);
}
});

I'm not exactly sure how the node.js 'path' and the bitshares config 'htdocs' elements function, so I feel the issue might stem from them. Also, perhaps the rpc method names are different from the hooks in the interactive client? If they are, are they documented anywhere?

5
Stakeholder Proposals / Re: The Big List of Delegates
« on: July 25, 2014, 11:22:51 pm »
btsx.chinesecommunity ripplexiaoshan faucet The faucet is for new users from China 50% 25% 99.5% 0.2.3


Updated. Thanks

Thank you! Sorry about the confusion.

6
Stakeholder Proposals / Re: The Big List of Delegates
« on: July 25, 2014, 10:31:31 am »
spartako update:

spartako spartako reliability low pay rate, high reliability 50% 50% 99% 0.2.3

Robohash:
http://robohash.org/spartako.png?size=64x64


Are you giving away half of your 50% payrate? In other words, are you taking 25% pay? Or did you mean 100% of a 50% payrate?

7
Stakeholder Proposals / Re: The Big List of Delegates
« on: July 25, 2014, 04:16:52 am »
Hey guys, just got back from work, but I'm updating the list right now.

I'm also going to be removing 'profit' as a category by request, and I will not be listing any delegates who's primary platform is voter profit, as I believe this may be a very real threat to BTSX. If you disagree, I would love to be proven wrong in this thread as I like the idea of profit-focused delegates, but not the idea of a homogeneous congress of 101 profiteers.

Thanks for putting me on the list.  :) I did miss a couple of blocks this morning while upgrading to 0.2.2 but still 99% reliability. And now on the latest version with bug fixes.

Cool, I'll update it! I picked you because you only had 1 delegate (I'm lazy and didn't want to add xeroc's 20 delegates...), you fit well into a category, and you seem like a good delegate.

Quote
Me too, that's why I only give the "faucet" yellow, instead of all the text, otherwise people are hardly to recognize them.

How about lime green? (Since I'm getting rid of profit.)

It would be nice if you added an extra column:   Version  that indicates what version the delegate is running.

Great idea! Is there a way for me to retrieve that info from the client? Or do I have to rely on the delegate to tell the truth?

btsx.chinesecommunity        ripplexiaoshan        faucet         The faucet is for new users from China  50%  25%  99%

Place the robohash on the list :)

Please format this using the template I provided. (I'd do your's for you bytemaster, because I know you're busy, but I don't actually know what robohash's function is.)

Done. Thanks, l like lime green ;)

Please use this template, including links to your forum thread and your forum profile:

Code: [Select]
[tr]
[td][color=COLOR][url=https://bitsharestalk.org/index.php?topic=TOPICNUM] DELEGATE [/url][/color][/td]
[td][color=COLOR][url=https://bitsharestalk.org/index.php?action=profile;u=USERNUM] USER [/url][/color][/td]
[td][color=COLOR] CATEGORY [/color][/td][td][color=COLOR] DESCRIPTION [/color][/td]
[td][color=COLOR] PAY RATE [/color][/td]
[td][color=COLOR] OWNER PAY RATE [/color][/td]
[td][color=COLOR] RELIABILITY [/color][/td]
[td][color=COLOR] VERSION [/color][/td]
[/tr]

Replace the words in caps.

8
Stakeholder Proposals / Re: The Big List of Delegates
« on: July 24, 2014, 11:35:38 pm »
Hey guys, just got back from work, but I'm updating the list right now.

I'm also going to be removing 'profit' as a category by request, and I will not be listing any delegates who's primary platform is voter profit, as I believe this may be a very real threat to BTSX. If you disagree, I would love to be proven wrong in this thread as I like the idea of profit-focused delegates, but not the idea of a homogeneous congress of 101 profiteers.

Thanks for putting me on the list.  :) I did miss a couple of blocks this morning while upgrading to 0.2.2 but still 99% reliability. And now on the latest version with bug fixes.

Cool, I'll update it! I picked you because you only had 1 delegate (I'm lazy and didn't want to add xeroc's 20 delegates...), you fit well into a category, and you seem like a good delegate.

Quote
Me too, that's why I only give the "faucet" yellow, instead of all the text, otherwise people are hardly to recognize them.

How about lime green? (Since I'm getting rid of profit.)

It would be nice if you added an extra column:   Version  that indicates what version the delegate is running.

Great idea! Is there a way for me to retrieve that info from the client? Or do I have to rely on the delegate to tell the truth?

btsx.chinesecommunity        ripplexiaoshan        faucet         The faucet is for new users from China  50%  25%  99%

Place the robohash on the list :)

Please format this using the template I provided. (I'd do your's for you bytemaster, because I know you're busy, but I don't actually know what robohash's function is.)

9
General Discussion / Preventing Destructive Profiteering
« on: July 24, 2014, 11:16:47 pm »
Right now, I think there are two major threats to BTSX. The first is false names which phish for votes. I3 already has plans to address this in ways which seem adequate. The larger threat, however, is profiteering. Once BTSX leaks out of our little community, people are going to start voting, not for delegates which are reliable or which hope to improve BTS/the BTS community, but rather, for delegates who give them a portion of their pay in exchange for votes. Essentially, we run the risk of turning BTSX into just a Rube Goldberg franken-cryptocurrency, rather than a cryptoequity platform. I fear that, if this is not addressed, this will destroy BTS. Especially with slate delegation on the way. I can just see the profiteering easy lists now.

Now, there is no way, as I understand, to tell who has voted for who directly through the client. However, an inspection of the blockchain which reveals this information would be trivial. I have two suggestions as to how to solve this problem, though I'm not sure if either of these could even work.

The first is to build mixing directly into the blockchain for votes only. If this is possible, it would make an effective inspection of the blockchain theoretically challenging and practically impossible. The second solution is to look at however the hell darkcoin works, and apply their anonymous transaction algorithm to BTSX voting.

By making voting anonymous, we kind of have the best of both worlds. People can still engage in 1  on 1 exchanges (e.g., vote for me and then post in this thread and I'll give you 300 dogecoin) which would encourage new delegates, encourage participating in the community, make more people aware of BTS, and increase the total number of cryptotransactions. However, it would be very difficult to do this on an industrial, impersonal scale and essentially operate a delegate as if it were a mining pool.

To me, this seems like a much more devastating issue than fake names. While the latter is harmful, it wont destroy BTSX and the vast majority of users agree that its bad. However, the former really could break BTSX, and once people have started to use BTSX in this way, it will become difficult to convince them to go along with a fork that removes their ability to profit. This is a ticking time bomb.

11
Stakeholder Proposals / The Big List of Delegates
« on: July 24, 2014, 05:15:38 am »
This is a thread dedicated to listing and organizing the delegates on this forum. I'm keeping it grouped by owner, and I've color coded each delegate according to which of these categories they best fit into:

enhancement: These delegates intend to use their pay to improve BTS itself, rewarding the entire community.
investment: These delegates plan to invest their pay into projects, circulating BTSX.
reliability: These delegates campaign primarily on their reliability rate. High reliability rates make for a fast, slim, and secure blockchain.
faucet: These delegates plan to give away their pay, giving new users some BTSX to play with.
service: These delegates provide some sort of service in exchange for your vote.
charity: These delegates give their pay to charity.
give away: These delegates will give you something upfront in exchange for your vote.
political: These delegates will dedicate their pay to some sort of political goal.
other: These delegates perform some other sort of function.

The 'owner' is the forum name of the person who controls the delegate, and the 'owner pay rate' is the amount of BTSX the delegate keeps for herself.

Why do we need this thread if we can list delegates through the client? This provides an easy way to find delegates who are at least minimally engaged with the community, and clearly conveys what function they provide.

name owner category description pay rate owner pay rate reliability version
btsx.chinesecommunity ripplexiaoshan faucet The faucet is for new users from China 50% 25% 99.5% 0.2.3
bdnoble bdnoble1206 reliability Please vote for bdnoble: High Reliability 99% 100% 99% 0.2.3
delegate-1.eightbit 8bit service You give me votes, and I'll give you with horrible art! 80% 100% N/A 0.2.1
commonwealth 8bit enhancement Giving back to the bitshares community with a 0% pay rate. 0% 0% 92% 0.2.1
spartako spartako reliability low pay rate, high reliability 50% 100% 99% 0.2.3
calabiyau calabiyau enhancement Supporting Swiss Node 95% 5% 99.5% 0.2.3
neuronics calabiyau Enhance Supporting Swiss Node 90% 10% 0% 0.2.3

Please post in this thread if you'd like to be added. Include your formatted rows, as that's annoying and time consuming for me to do. Here's a template you can use:

Code: [Select]
[tr]
[td][color=COLOR][url=https://bitsharestalk.org/index.php?topic=TOPICNUM] DELEGATE [/url][/color][/td]
[td][color=COLOR][url=https://bitsharestalk.org/index.php?action=profile;u=USERNUM] USER [/url][/color][/td]
[td][color=COLOR] CATEGORY [/color][/td][td][color=COLOR] DESCRIPTION [/color][/td]
[td][color=COLOR] PAY RATE [/color][/td]
[td][color=COLOR] OWNER PAY RATE [/color][/td]
[td][color=COLOR] RELIABILITY [/color][/td]
[td][color=COLOR] VERSION [/color][/td]
[/tr]

Replace everything in caps.

If your campaign involves using your funds in a certain way, please provide either A.) evidence of past performance or B.) evidence that you will provide evidence in the future. I will use discretion when adding people to the list, and I will not add accounts that I suspect might be scams.

12
General Discussion / Re: Theres an IRC channel. Why aren't you in it?
« on: July 24, 2014, 03:29:55 am »
There's a "chat" link at the top of the forum. I tried to push it and gave up. Hard to remember to go there.

Aw shit, you're right.

It might be helpful to add it to the the 'community' section on the landing site as well, as that's where I looked for it.

13
All right, so I was an active delegate for 18 blocks and I missed them all because I didn't have block production turned on. :(

But it's fixed now!

Quote from: CLains
+5%

The goal of this delegate would be to make that a +6%, actually. :)

14
General Discussion / Theres an IRC channel. Why aren't you in it?
« on: July 24, 2014, 12:47:15 am »
Srsly guys, get your shit together.

network: irc.freenode.org
channel: #bitshares

If you don't have an IRC client you can use the web client by clicking here. Just enter #bitshares as the channel name and your forum name (or a different nick of your choice) as your nick, enter the CAPTCHA, and then click connect.

I'm the8thbit and the8thbit|work on the IRC.

15
Can I delegate my vote to non-delegates? Building a quality slate seems like a good way to convince the community that you're dedicated to bitshares.

Can I have votes that I personally make take priority over those I delegate my votes to? So for example, I vote for 5 people, and then subscribe to a slate of 101 people. Will the system vote for my 5, and then bump out 5 of the 101 randos I just signed up for?

Can I 'block' delegates? So, for example, I subscribe to a slate containing the delegate doucheBagKyle, but I have doucheBagKyle blocked, so I don't vote for him even though I just subscribed to a slate containing him.

If yes to the above, can people make slates that block people, rather than vote for them?

Pages: [1] 2 3 4