Author Topic: Dry Run 6: Great Scott!  (Read 90974 times)

0 Members and 1 Guest are viewing this topic.

Offline dxtr

  • Full Member
  • ***
  • Posts: 71
  • United We Stand, Dispersed We Are.
    • View Profile
Please, can I get some XTS so I can put my delegate a few spots higher?

Public key:XTS6hjYfVGrPDFKQc5oLTVp5rU56m15XnEvVCtzMLkyDMni2rentc
Account name: dxtr


Also, when are delegates' funds supposed to be available for them to spend? After every round is over or some other moment?

Thanks.
« Last Edit: June 30, 2014, 03:04:19 pm by dxtr »
Help me out:     wallet_approve_delegate mr.scroodge true

Offline CalabiYau

Latest windows binaries have been posted, now at version 0.0.7
error.
unable to execute file:
\bin\qt_wallet.exe

Gyhy,
What is your Windows version? If this is XP - it's not supported in by the latest Microsoft compiler in VS 2013.
 

Same error,  WIN7 / 64

Offline dexinwong

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
pls give me some bts

XTS7MwVJTP6ztKKugmJxbUqCnz9yKCC4MbpTyFE9P3PNVF914TUxE

Send  6 XTS.

Offline rzshenwei

  • Full Member
  • ***
  • Posts: 89
    • View Profile
pls give me some bts

XTS7MwVJTP6ztKKugmJxbUqCnz9yKCC4MbpTyFE9P3PNVF914TUxE

Offline dexinwong

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
Code: [Select]
>> blockchain_list_forks

   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
           1860
     5a1cee648bf5a393100f055d2557ac5de6300d50                        init68              0       182 2014-06-30T04:40:00         2     YES                  NO
     20da07a55e88984bf5eae3a5c2c290b0e7cc12b4                       vikram6              0       182 2014-06-30T04:28:00       928     YES                 YES
           1866
     29c6afe97be1d21e18f3243a3fd0a1c53b478ab2                      alexxy-1              0       182 2014-06-30T04:46:00         2     YES                  NO
     a5362f194766468442e4a8f84d8afe0219093584                       vikram8              0       182 2014-06-30T04:44:00       762     YES                 YES

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
After restarting the client yesterday everything was fine for about 3 rounds.
Then my delegates began missing blocks. There were no error messages.

UPDATE: My delegates are still missing blocks even after restart.
list_errors shows nothing.
What should I do about it?
« Last Edit: June 30, 2014, 06:31:39 am by emski »

Offline dexinwong

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
plz give me a little    :)
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs

Sent you some play money

Thx your 20 XTS    :)

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
plz give me a little    :)
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs

Sent you some play money
>>> approve bitcoiners

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
some funds pls XTS7WVjY2PkkMQygDdFPEFjueZ1Ky1orLgU3XSaSpdv8EkTLyy6Sy (bambule) thx

Sent you some XTS and Dots
>>> approve bitcoiners

Offline dexinwong

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
plz give me a little    :)
XTS6TtY8Mf97nyqtqjRg94NobLY15Korc3XNXFzkuXj1oiTex5GNs

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
some funds pls XTS7WVjY2PkkMQygDdFPEFjueZ1Ky1orLgU3XSaSpdv8EkTLyy6Sy (bambule) thx
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline vikram

In the latest commit, I have renamed wallet_set_delegate_trust to wallet_approve_delegate, so now the command to approve a delegate is:
Code: [Select]
wallet_approve_delegate <delegate_name> true

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
Hi BM  and Toast ,

2 programers from Chinese community would like to make a suggestion for you to use    "EPaxos" for helping to resolve our forking issues due to limited bandwidth and slow hardware performance of our delegates .
   
https://github.com/efficient/epaxos

Iulian Moraru, David G. Andersen -- Carnegie Mellon University

Quote


EPaxos
What is EPaxos?

EPaxos is an efficient, leaderless replication protocol. The name stands for Egalitarian Paxos -- EPaxos is based on the Paxos consensus algorithm. As such, it can tolerate up to F concurrent replica failures with 2F+1 total replicas.
How does EPaxos differ from Paxos and other Paxos variants?

To function effectively as a replication protocol, Paxos has to rely on a stable leader replica (this optimization is known as Multi-Paxos). The leader can become a bottleneck for performance: it has to handle more messages than the other replicas, and remote clients have to contact the leader, thus experiencing higher latency. Other Paxos variants either also rely on a stable leader, or have a pre-established scheme that allows different replicas to take turns in proposing commands (such as Mencius). This latter scheme suffers from tight coupling of the performance of the system from that of every replica -- i.e., the system runs at the speed of the slowest replica.

EPaxos is an efficient, leaderless protocol. It provides strong consistency with optimal wide-area latency, perfect load-balancing across replicas (both in the local and the wide area), and constant availability for up to F failures. EPaxos also decouples the performance of the slowest replicas from that of the fastest, so it can better tolerate slow replicas than previous protocols.
How does EPaxos work?

We have an SOSP 2013 paper that describes EPaxos in detail.

A simpler, more straightforward explanation is coming here soon.
What is in this repository?

This repository contains the Go implementations of:

    Egalitarian Paxos (EPaxos), a new distributed consensus algorithm based on Paxos EPaxos achieves three goals: (1) availability without interruption as long as a simple majority of replicas are reachable---its availability is not interrupted when replicas crash or fail to respond; (2) uniform load balancing across all replicas---no replicas experience higher load because they have special roles; and (3) optimal commit latency in the wide-area when tolerating one and two failures, under realistic conditions. Egalitarian Paxos is to our knowledge the first distributed consensus protocol to achieve all of these goals efficiently: requiring only a simple majority of replicas to be non-faulty, using a number of messages linear in the number of replicas to choose a command, and committing commands after just one communication round (one round trip) in the common case or after at most two rounds in any case.

    (classic) Paxos

    Mencius

    Generalized Paxos

The struct marshaling and unmarshaling code was generated automatically using the tool available at: https://code.google.com/p/gobin-codegen/

The repository also contains a machine-readable (and model-checkable) specification of EPaxos in TLA+.

AUTHORS:

Iulian Moraru, David G. Andersen -- Carnegie Mellon University

Michael Kaminsky -- Intel Labs


EPAXOS 作者是Toast学校的。
硬件不足,软件补。赞赏这个设计,目前的网络体系架构并不适合网络货币的需求,需要在软件上做补偿设计。

是啊,这两天看了EPAXOS算法,这货=DPOS+现在BM正在搞得代表之间协议啊。如果BM能完成的质量高可以,还是分叉严重的话谁能帮忙给BM推荐参考一下这算法?哪位大侠能直接跟BM沟通。
https://github.com/efficient/epaxos

转hackfisher 或直接pm bm吧
« Last Edit: June 29, 2014, 09:09:36 pm by sfinder »
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students

Offline alexxy

  • Full Member
  • ***
  • Posts: 175
    • View Profile
Latest git master crashes with segfault. Backtrace included
Code: [Select]
(wallet closed) >>>
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff1062700 (LWP 12202)]
0x00007ffff49913d3 in std::_Rb_tree_increment(std::_Rb_tree_node_base const*) () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0/libstdc++.so.6
(gdb) bt
#0  0x00007ffff49913d3 in std::_Rb_tree_increment(std::_Rb_tree_node_base const*) () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0/libstdc++.so.6
#1  0x0000000000bf3dd4 in operator++ (this=<synthetic pointer>) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0/include/g++-v4/bits/stl_tree.h:283
#2  CEPoll::update_events (this=0x154c268 <CUDT::s_UDTUnited+488>, uid=@0x7fffe0000ad0: 969631102,
    eids=std::set with 576 elements<error reading variable: Cannot access memory at address 0x5b3a22736e6f698c>, events=events@entry=8, enable=enable@entry=true)
    at /home/alexxy/Src/bitshares_toolkit/libraries/fc/vendor/udt4/src/epoll.cpp:345
#3  0x0000000000bf8b8b in CRendezvousQueue::updateConnStatus (this=0x1591e30) at /home/alexxy/Src/bitshares_toolkit/libraries/fc/vendor/udt4/src/queue.cpp:848
#4  0x0000000000bf9b2d in CRcvQueue::worker (param=0x155f0c0) at /home/alexxy/Src/bitshares_toolkit/libraries/fc/vendor/udt4/src/queue.cpp:1090
#5  0x00007ffff717b0d4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff4141c5d in clone () from /lib64/libc.so.6
(gdb) up
#1  0x0000000000bf3dd4 in operator++ (this=<synthetic pointer>) at /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.0/include/g++-v4/bits/stl_tree.h:283
283             _M_node = _Rb_tree_increment(_M_node);
(gdb) up
#2  CEPoll::update_events (this=0x154c268 <CUDT::s_UDTUnited+488>, uid=@0x7fffe0000ad0: 969631102,
    eids=std::set with 576 elements<error reading variable: Cannot access memory at address 0x5b3a22736e6f698c>, events=events@entry=8, enable=enable@entry=true)
    at /home/alexxy/Src/bitshares_toolkit/libraries/fc/vendor/udt4/src/epoll.cpp:345
345        for (set<int>::iterator i = eids.begin(); i != eids.end(); ++ i)
(gdb) up
#3  0x0000000000bf8b8b in CRendezvousQueue::updateConnStatus (this=0x1591e30) at /home/alexxy/Src/bitshares_toolkit/libraries/fc/vendor/udt4/src/queue.cpp:848
848                 CUDT::s_UDTUnited.m_EPoll.update_events(i->m_iID, i->m_pUDT->m_sPollID, UDT_EPOLL_ERR, true);
(gdb) up
#4  0x0000000000bf9b2d in CRcvQueue::worker (param=0x155f0c0) at /home/alexxy/Src/bitshares_toolkit/libraries/fc/vendor/udt4/src/queue.cpp:1090
1090          self->m_pRendezvousQueue->updateConnStatus();
(gdb) up
#5  0x00007ffff717b0d4 in start_thread () from /lib64/libpthread.so.0
(gdb) up
#6  0x00007ffff4141c5d in clone () from /lib64/libc.so.6

Git sumodule update?

already done. It was fixed by dropping all except wallet from ~/.BitSharesXTS dir
Vote for my delegates! alexxy | lexx
PTS: PmraxfZ852y9oEKrYMLX1ee3e4qRWPUTFC
BTS: alexxy

Offline sfinder

  • Hero Member
  • *****
  • Posts: 1205
  • 4 Cores CPU+100GB SSD+anti-DDoS Pro
    • View Profile
1) if you are confident then I do not need to worry... +5% +5% +5%
2) I have a suggestion that to show the delegate's client version info in the output list of  "blockchain_list_delegates"

Hi BM,
our testing chain is getting over 45 forks in a single day . is it normal ? can you give us some updates on the testing status?

Thanks

45 forks is not normal operation and is a result of bugs in the networking code.  I will have Eric look into the cause when he comes in on Monday.   In the mean time my primary objective of this stress/test with extreme forking is to view the bugs as the most extreme form of network problem we could experience.  Despite having 45 forks in a single day, the network has maintained consensus and all transactions have been confirmed.

It is very ugly but based upon the nature of the bugs I am seeing I am confident that we will be fork-free in the next few days.
微博:星在飘我在找|BTS X 受托人delegate ID:baidu
中国教育书店合作将20%收入捐献给贫困山区学生。
Cooperating with China Education Bookstore and will donate 20% of delegate income to the poor students