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

Pages: 1 ... 814 815 816 817 818 819 820 [821] 822 823 824 825 826 827 828 ... 860
12301
General Discussion / Re: TITAN Test Net for XTS Open for Savvy Users
« on: June 03, 2014, 07:21:46 am »
Finally my machine connects to the network. What ever went wrong the last time, its working this time:

please send some to

XTS72E5WHYP79vY4FuNZB4eVUs4hw71Aynr3Cv8CB9e2rQWJpB57q

12302
General Discussion / Re: noteworthy events
« on: June 03, 2014, 07:19:09 am »
Wow... How could I miss this thread. Thanks for Bumping

EDIT: Brian!!! WE NEED AN (TECH) ARTICLE THERE!

12303
My 2PTS,

I give a $"§%§ about others complaining about the progress. They clearly cannot read the git commit logs.

12304
+5% .. speaking truth

12305
Stakeholder Proposals / Re: Candidate Billboards
« on: June 02, 2014, 02:40:42 pm »
Hey there,

I am an active (and for the last few weeks, very active) user on this board. As you can see
from my userid I joined in 'the early days' and still stick around as this is one of the nicest
communities around. Further, the ecosystem behind bitshares is fascinating and the technical
ideas BM has and implements are awesome.
For the trust: Hm, I guess I am trustworthy, as I did some successful trade on this board, and
BTT (trust ratings). If you want to know more about me in person, I am not hiding my real name
(as some of you already know) but I also do not post my private details publicly (+except on
my own webpage, which can be found via my username :-)  )

For the moment I will host bitshares on a vMachine of my dedicated server:
Server: dedicated, 8 GB RAM, 2TB disk, 4 CPUs
Location: Germany

12306
Sorry for chiming in, I just opened a new board for all delegate issues. It will help everyone to find the place discuss about campaign, election, attacks and service.
+5%

12307
Quote

Sweet .. but why the rounded corners?

12308
Odd, I had between 4/5 connections up until block 930 and now I can't connect anymore.
I have compiled the latest git revision, but that does not seem to want to connect either.

What method are people using to update from git and recompiling? Just running make clean doesn't seem to work for me, but deleting all contents by hand and redownloading is not particularly efficient.
I'd say the guys at 3i are working on the seed node:
Quote
944004ms       th_a           connect_to ] fatal: error connecting to peer 107.170.30.182:5678: unspecified
Connection refused
    {"message":"Connection refused"}
    asio  asio.cpp:56 error_handler
Seed node seems to be down

12309
General Discussion / Re: New truthcoin forum
« on: June 02, 2014, 08:22:47 am »
I am too, but I was asking about Dan and co. Maybe you're part of that co. though.
I am not :-|

12310
Technical Support / Re: AGS potential security issue
« on: June 02, 2014, 07:18:03 am »
We already have a tool that parses one address, that's the hard word and it's been done. Parsing a second one is trivial.
True.
Quote
EDIT: I might have misunderstood. Did you mean we can't parse multiple output transactions? :)
Why should we not. Sure we can. Having multiple inputs might be an issue, but sending 1 satoshi can be done with one input easily :-)

12311
General Discussion / Re: New truthcoin forum
« on: June 02, 2014, 06:59:58 am »
If the community is the same can't we just have the discussions here? Maybe make it even a main subforum istead of a child board.

Is I3 still interested in this?
I am!

12312
Technical Support / Re: AGS potential security issue
« on: June 02, 2014, 06:59:06 am »
I missed that detail, but my solution still works. Let me provide more info.

Make a special 1_AGS_TRANSFER BTC address.

When you want to send a "TRANSFER TO xxx" message as a transaction do this:

Send 0.01 BTC (or whatever fee BM thinks is appropriate, or if generous make it 1 satoshi) to the 1_AGS_TRANSFER address.
In the same transaction send 1 satoshi to the new BTC address that will control your AGS

So you have

INPUT:
OLD_DONOR_ADDRES

OUTPUTS:
1_AGS_TRANSFER | AMT: FEE (say 0.01BTC)
1_NEW_DONOR_ADDRESS | AMT: 1 satoshi

This is totally doable. Parser generating genesis addresses would need to be adjusted to look for 1_AGS_TRANSFER as well.
Much like satoshi dice ...

Can work .. however. To generate a new genesis block for new DACs you now need to pars 2 addresses .. that is an overhead.

But still, nice solution!

12313
I may now know a possible reason for my machine not connecting to the network.
My Maschine uses XEN for virtualizing and I set up routing for the machine like (debian network interface)
Quote
auto eth0
iface eth0 inet static
  address PUBLIC-IP
  netmask 255.255.255.255
  gateway MY-XEN-DOMU
  pointopoint MY-NEXT-HOP
As a result:
Quote
route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         myGW    0.0.0.0         UG    0      0        0 eth0
10.0.0.0        10.0.0.2        255.255.255.0   UG    0      0        0 tun0
10.0.0.2        0.0.0.0         255.255.255.255 UH    0      0        0 tun0
myGW    0.0.0.0         255.255.255.255 UH    0      0        0 eth0

Further more on the DOM-U (the host machine):
Quote
net.ipv4.ip_forward=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.icmp_echo_ignore_broadcasts=1
net.ipv4.conf.default.proxy_arp = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.all.proxy_ndp = 1


See a german tutorial here: http://wiki.hetzner.de/index.php/Umstellung_Xen_3_auf_routed

12314
FreeTrade also made a very nice suggestion:
https://bitsharestalk.org/index.php?topic=4737.msg61342#msg61342

12315
Technical Support / Re: AGS potential security issue
« on: June 02, 2014, 06:39:35 am »
Sending messages over bitcoin network is not possible.
Blockchain.info is just a centralized service that one can use to send a message. or are you proposing the use of OP_RETURN?

Pages: 1 ... 814 815 816 817 818 819 820 [821] 822 823 824 825 826 827 828 ... 860