Bitcoin Forum
November 17, 2018, 04:32:33 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 ... 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 [363] 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 »
  Print  
Author Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come  (Read 754737 times)
pfft
Full Member
***
Offline Offline

Activity: 172
Merit: 100


View Profile
March 18, 2018, 12:20:43 AM

If your wallet is locked you have to unlock it for minting only or full unlock.
I don`t have my wallet locked.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542472353
Hero Member
*
Offline Offline

Posts: 1542472353

View Profile Personal Message (Offline)

Ignore
1542472353
Reply with quote  #2

1542472353
Report to moderator
1542472353
Hero Member
*
Offline Offline

Posts: 1542472353

View Profile Personal Message (Offline)

Ignore
1542472353
Reply with quote  #2

1542472353
Report to moderator
pfft
Full Member
***
Offline Offline

Activity: 172
Merit: 100


View Profile
March 18, 2018, 12:23:19 AM

Any one can help me please why the miner cannot connect?


try another miner

go to discord channel and download the miner from there
Can you share me the link please ?
okamuwf
Full Member
***
Offline Offline

Activity: 322
Merit: 105


View Profile
March 18, 2018, 01:28:42 AM

Any one can help me please why the miner cannot connect?


try another miner

go to discord channel and download the miner from there
Can you share me the link please ?

https://discord.gg/hhprtwt/
pfft
Full Member
***
Offline Offline

Activity: 172
Merit: 100


View Profile
March 18, 2018, 02:26:51 AM

Any one can help me please why the miner cannot connect?


try another miner

go to discord channel and download the miner from there
Can you share me the link please ?

https://discord.gg/hhprtwt/

It`s not working i see it in the first page...
Guys from where we can download oracle wallet because on their website is only old wallet.. ?
pfft
Full Member
***
Offline Offline

Activity: 172
Merit: 100


View Profile
March 20, 2018, 02:02:53 AM

Anyone can help me how can i contact any of team from this pool
https://nexuspool.ru/?account=2Rhvn8SwAUjzMr2TtfGJhcep83vQNqhkiDRzCaWuzaYpDC9Nwwk
I mine few coins and i don`t receive nothing in my wallet yet...
http://i67.tinypic.com/eaqi2p.jpg
http://i63.tinypic.com/2mcdms3.jpg
jezabel
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
March 20, 2018, 02:15:01 AM

anyone mining solo? 3 days with 3x1080 ti and 5x1070 ti and I didn't find any blocks !! last week I found 5 blocks in the same time period

Variance has no remorse..

You got lucky and then you were unlucky. It's really as simple as that.
If the mining program you have, found you 5 solo blocks, it works. If you really have doubts, re-start the miner. If it connects then you are fine.
stan86
Hero Member
*****
Offline Offline

Activity: 1050
Merit: 511



View Profile
March 20, 2018, 04:55:18 AM

Nexus is happy to Announce the Integration of the LISP

Network Architecture which allows

The Nexus Blockchain to run over a Secure Open Overlay

Read about it Here Now: https://nexusearth.com/news/nexus-integration-with-the-lisp-network-architecture/


                 ██            ██
               ██████        ██████
            ████████████      ██████
        ███████████████████    ██████
     ███████████    ██████████  ██████
  ██████████    ███    ████████  ▀█████
  ██████    ███████████   ██████  █████
  █████   ██████  ██████   █████  █████
  █████    ███      ███    █████  █████
  █████  ██            ██  █████  █████
  █████  ███          ███  █████  █████
  █████  ███████   ██████  █████  █████
  █████  ████████████████  █████  █████
  █████  ████████████████  █████  █████
  █████  ████  █████ ████  ████  ██████
  █████  ████   ███  ████  ███  ██████
  █████  ████    █   ████  █   ██████ 
  █████  ████        ██      ███████     
    ███  ████        █     ███████         
      █  ████         ▄██  █████       
           ██        ████  ███
            █        ██▀
`AiBB`  覧覧覧覧覧
HARNESSING THE POWER OF Ai IN CRYPTO
▐ -
`BUY TOKENS`
-▐   Twitter
  Telegram
  Facebook
|WP
Reddit
Medium
Isle of Groestl
Member
**
Offline Offline

Activity: 154
Merit: 10


View Profile
March 20, 2018, 09:27:40 AM

Nexus is pleased to announce the integration of the LISP (Locator Identity Separation Protocol) network architecture with Nexus Earth which allows the Nexus blockchain to run over a secure open overlay.  LISP was created by Dino Farinacci, in partnership with several Cisco engineers, and is being developed and standardized by the Internet Engineering Task Force (IETF).  Dino founded lispers.net after being a Cisco Fellow. At Cisco Systems he designed and implemented dozens of protocols: 杜ore than anyone on earth.

LISP helps the internet scale, and provides secure features for today痴 newer applications, by encapsulating a packet with identifiers into a packet with topological locators.  This allows the internet to route packets based on location rather than identifiers, enabling it to scale by holding less routing state.  As the lispers.net website explains: 展e are building state-of-the art, next generation internet architectures and protocols that enable modern-use applications to scale securely and run efficiently.

The Ciscso website notes: 鏑ISP is a network architecture and set of protocols that implements a new semantic for IP addressing.  LISP creates two namespaces and uses two IP addresses: Endpoint Identifiers (EIDs), which are assigned to end-hosts, and Routing Locators (RLOCs), which are assigned to devices (primarily routers) that make up the global routing system.

Why is this Important

The network keeps growing with the expanding number of users and devices (think wireless phone, computers, wireless earbuds, iPads etc) so we need to have a way to consolidate data in order for the network to handle more traffic from more devices.  Our internet currently runs on IPv4 which can handle 4.3 billion IP addresses, fewer than the number of people in the world. Once you add in multiple devices you can see where the current system needs to scale, and thus IPv6 comes into play.  However the transition to IPv6 started in 1990 and is still not completed.  LISP allows identifiers to be IPv6 addresses while the core does not have to be completely converted to IPv6 so we can address 2^128 nodes (3.4E38 addresses), close to addressing every particle (1.33E50) on earth (off by 10^12).

You can read more about IPv4 and IPv6 here:

https://www.nbcnews.com/news/us-news/internet-now-officially-too-big-ip-addresses-run-out-n386081

LISP also speeds up the user experience, as we currently don稚 take the shortest path between communication devices with intermediaries such as ISPs.  LISP provides increased speed & scalability.

Taking the shortest path between devices has additional implications.  Peer to peer, or direct device to device, communication equates to a more secure, decentralized network mitigating delays and connection interruptions.  The devices that attach to the network will have multiple connections and continuously be moving around.  We want applications to keep their connections up during roaming, mitigating latency.

How LISP Works Exactly

With LISP the user receives an EID (end-point ID), which is a static Identity.  Instead of your identity changing each time you move your devices, it stays fixed and encrypted, allowing everything to run more smoothly.  Comparing this to blockchain, your EID basically becomes the 鍍rust key for your identity.  This EID or address is the same address you would be using today on your devices, but the address can remain assigned to you and is independent of how and where you connect to the network.  An EID can be a 鼎rypto-EID, so when a private/public key-pair is allocated to the device, the Crypto-EID is a hash of the public-key.  Therefore, your identity is based on your crypto credentials, much like your Nexus Wallet address.

LISP & Nexus

For the last few months Nexus has been successfully test running two Nexus nodes, Nexus 1 & Nexus 2, that have been assigned EIDs and are using the LISP overlay.

How LISP helps Nexus

Just a single feature of LISP benefits Nexus, but there are many.  LISP allows Nexus to have all of its data packets encrypted when traveling over the network.  With LISP providing a direct route for information to travel there are no eavesdroppers in the middle of information transfer, providing privacy of transactions.  Did you know that disclosing your physical location is a privacy issue?  LISP is essentially bringing HTTPS (Hyper Text Transfer Protocol Secure) level security to Nexus.

Another way that LISP enhances Nexus is by running the blockchain over IPv6 even if the whole internet is not running on it.  Nexus runs on an IPv6 overlay where LISP will allow it to connect to the IPv4 underlay.

Nexus & LISP at the Internet Engineering Task Force 101

Colin Cantrell, Chief Architect and founder of Nexus will be speaking with Dino Farinacci on Monday March 19th at The Internet Engineering Task Force (IETF) 101 in London on LISP and the future of blockchain technology.

For more tech detail, please visit this draft published to IETF by Colin Cantrell & Dino Farinacci:

https://datatracker.ietf.org/doc/draft-farinacci-lisp-decent/

https://nexusearth.com/news/nexus-integration-with-the-lisp-network-architecture/
Isle of Groestl
Member
**
Offline Offline

Activity: 154
Merit: 10


View Profile
March 20, 2018, 08:22:07 PM

Here is the draft of the paper Colin and Dino wrote together if anyone missed it:
https://datatracker.ietf.org/doc/draft-farinacci-lisp-decent/


Network Working Group                                       D. Farinacci
Internet-Draft                                               lispers.net
Intended status: Experimental                                C. Cantrell
Expires: July 14, 2018                                             Nexus
                                                        January 10, 2018

               A Decent LISP Mapping System (LISP-Decent)
                     draft-farinacci-lisp-decent-00

Abstract

   This draft describes how the LISP mapping system designed to be
   distributed for scale can also be decentralized for management and
   trust.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 14, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Farinacci & Cantrell      Expires July 14, 2018                 [Page 1]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition of Terms . . . . . . . . . . . . . . . . . . . . .   2
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Components of a LISP-Decent xTR . . . . . . . . . . . . . . .   5
   5.  No LISP Protocol Changes  . . . . . . . . . . . . . . . . . .   6
   6.  Configuration and Authentication  . . . . . . . . . . . . . .   6
   7.  Core Peer-Group . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     10.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  10
   Appendix B.  Document Change Log  . . . . . . . . . . . . . . . .  10
     B.1.  Changes to draft-farinacci-lisp-decent  . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The LISP architecture and protocols [RFC6830] introduces two new
   numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
   (RLOCs) which is intended to provide overlay network functionality.
   To map from EID to a set or RLOCs, a control-plane mapping system are
   used [RFC6836] [RFC8111].  These mapping systems are distributed in
   nature in their deployment for scalability but are centrally managed
   by a third- party entity, namely a Mapping System Provider (MSP).
   The entities that use the mapping system, such as data-plane xTRs,
   depend on and trust the MSP.  They do not participate in the mapping
   system other than to register and retrieve information to/from the
   mapping system [RFC6833].

   This document introduces a Decentralized Mapping System (DMS) so the
   xTRs can participate in the mapping system as well as use it.  They
   can trust each other rather than rely on third-party infrastructure.
   The xTRs act as Map-Servers to maintain distributed state for scale
   and reducing attack surface.

2.  Definition of Terms

   Decentralized Mapping System (DMS):  is a mapping system entity that
      is not third-party to the xTR nodes that use it.  The xTRs
      themselves are part of the mapping system.  The state of the
      mapping system is fully distributed, decentralized, and the trust
      relies on the xTRs that use and participate in their own mapping
      system.

Farinacci & Cantrell      Expires July 14, 2018                 [Page 2]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

   Mapping System Provider (MSP):  is an infrastructure service that
      deploys LISP Map-Resolvers and Map-Servers [RFC6833] and possibly
      ALT-nodes [RFC6836] or DDT-nodes [RFC8111].  The MSP can be
      managed by a separate organization other than the one that manages
      xTRs.  This model provides a business separation between who
      manages and is responsible for the control-plane versus who
      manages the data-plane overlay service.

   Peer-Group:  is a set of Map-Servers which are joined to the same
      multicast group that send and receive Map-Register messages
      addressed to the multicast group.  Map-Resolvers can use the peer-
      group to resolve mappings by sending Map-Requests to the multicast
      group or to any member of the peer-group.  Map-Resolvers can do a
      mapping system lookup for the peer-group multicast address to
      obtain members of the peer-group.

   Core Peer-Group:  is a set of Map-Servers and Map-Resolvers who are
      joined to a multicast group to bootstrap a multi-layer
      decentralized mapping system.

   Replication List Entry (RLE):  is an RLOC-record format that contains
      a list of RLOCs that an ITR replicates multicast packets on a
      multicast overlay.  The RLE format is specified in [RFC8060].

   Group Address EID:  is an EID-record format that contains IPv4
      (0.0.0.0/0, G) or IPv6 (0::/0, G) state.  This state is encoded as
      a Multicast Info Type LCAF specified in [RFC8060].  Members of a
      peer-group send Map-Registers for (0.0.0.0/0, G) or (0::/0, G)
      with an RLOC-record that RLE encodes its RLOC address.  Details
      are specified in [I-D.ietf-lisp-signal-free-multicast].

3.  Overview

   The clients of the Decentralized Mapping System (DMS) are also the
   providers of mapping state.  Clients are typically ETRs that Map-
   Register EID-to-RLOC mapping state to the mapping database system.
   ITRs are clients in that they send Map-Requests to the mapping
   database system to obtain EID-to-RLOC mappings that are cached for
   data-plane use.  When xTRs participate in a DMS, they are also acting
   as Map-Resolvers and Map-Servers using the protocol machinery defined
   in LISP control-plane specifications [RFC6833], [I-D.ietf-lisp-sec],
   and [I-D.farinacci-lisp-ecdsa-auth].  The xTRs are not required to
   run the database mapping transport system protocols specified in
   [RFC6836] or [RFC8111].

   The xTRs are organized in a peer-group.  The peer-group is identified
   by an IPv4 or IPv6 multicast group address.  The xTRs join the same
   multicast group and receive LISP control-plane messages addressed to

Farinacci & Cantrell      Expires July 14, 2018                 [Page 3]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

   the group.  Messages sent to the multicast group are distributed when
   the underlay network supports IP multicast [RFC6831] or is achieved
   with the overlay multicast mechanism described in
   [I-D.ietf-lisp-signal-free-multicast].  When overlay multicast is
   used and LISP Map-Register messages are sent to a peer-group, they
   are LISP data encapsulated with a instance-ID set to 0xffffff in the
   LISP header.  The inner header of the encapsulated packet has the
   destination address set to the peer-group multicast group address and
   the outer header that is prepended has the destination address set to
   the RLOC of peer-group member.  The members of the peer-group are
   kept in the LISP data-plane map-cache so packets for the peer-group
   can be replicated to each member RLOC.

   All xTRs in a peer-group will store the same registered mappings and
   maintain the state as Map-Servers normally do.  The peer-group
   members are not only receivers of the multicast group but also send
   packets to the group.

Farinacci & Cantrell      Expires July 14, 2018                 [Page 4]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

4.  Components of a LISP-Decent xTR

   When an xTR is configured to be a LISP-Decent xTR (or PxTR
   [RFC6832]), it runs the ITR, ETR, Map-Resolver, and Map-Server LISP
   network functions.

   The following diagram shows 3 LISP-Decent xTRs joined to peer-group
   224.1.1.1.  When the ETR function of xTR1 originates a Map-Register,
   it is sent to all xTRs (including itself) synchronizing all 3 Map-
   Servers in xTR1, xTR2, and xTR3.  The ITR function can populate its
   map-cache by sending a Map-Request locally to its Map-Resolver so it
   can replicate packets to each RLOC for EID 224.1.1.1.

                        xTR1
 Map-Request    +--------------------+
(always local)  |  +-----+  +-----+  |
   +---------------| ITR |  | ETR |-------------+
   |            |  +-----+  +-----+  |          |
   |            |                    |          |    Map-Register to EID
   |            |      +-------+     |          |  224.1.1.1 encapsulated to
   +------------------>| MR/MS |<---------------+  RLOCs xTR1, xTR2, and xTR3
                |      +-------+     |          |
                +--------------------+          |
                                                |
                           +--------------------+------------+
                           |                                 |
                           |                                 |
                +----------v---------+            +----------v---------+
                |     +--------+     |            |     +--------+     |
                |     |  MR/MS |     |            |     |  MR/MS |     |
                |     +--------+     |            |     +--------+     |
                |  +-----+  +-----+  |            |  +-----+  +-----+  |
                |  | ITR |  | ETR |  |            |  | ITR |  | ETR |  |
                |  +-----+  +-----+  |            |  +-----+  +-----+  |
                +--------------------+            +--------------------+
                         xTR2                              xTR3

   Note if any external xTR would like to use a Map-Resolver from the
   peer-group, it only needs to have one of the LISP-Decent Map-
   Resolvers configured.  By doing a looking to this Map-Resolver for
   EID 224.1.1,1, the external xTR could get the complete list of
   members for the peer-group.

   For future study, an external xTR could multicast the Map-Request to
   224.1.1.1 and either one of the LISP-Decent Map-Resolvers would

Farinacci & Cantrell      Expires July 14, 2018                 [Page 5]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

   return a Map-Reply or the external xTR is prepared to receive
   multiple Map-Replies.

5.  No LISP Protocol Changes

   There are no LISP protocol changes required to support this LISP-
   Decent specification.  However, an implementation that sends Map-
   Register messages to a multicast group versus a specific Map-Server
   unicast address must change to call the data-plane component so the
   ITR functionality in the node can encapsulate the Map-Register as a
   unicast packet to each member of the peer-group.

   An ITR SHOULD lookup its peer-group address periodically to determine
   if the membership has changed.  The ITR can also use the pubsub
   capability documented in [I-D.rodrigueznatal-lisp-pubsub] to be
   notified when a new member joins or leaves the peer-group.

6.  Configuration and Authentication

   When xTRs are joined to a multicast peer-group, they must have their
   site registration configuration consistent.  Any policy or
   authentication key material must be configured correctly and
   consistently among all members.  When [I-D.farinacci-lisp-ecdsa-auth]
   is used to sign Map-Register messages, public-keys can be registered
   to the peer-group using the site authentication key mentioned above
   or using a different authentication key from the one used for
   registering EID records.

7.  Core Peer-Group

   A core peer-group multicast address can be preconfigured to bootstrap
   the decentralized mapping system.  The group address (or DNS name
   that maps to a group address) can be explicitly configured in a few
   xTRs to start building up the mappings.  Then as other xTRs come
   online, they can add themselves to the core peer-group by joining the
   peer-group multicast group.

   Alternatively or additionally, new xTRs can join a new peer-group
   multicast group to form another layer of a decentralized mapping
   system.  The group address and members of this new layer peer-group
   would be registered to the core peer-group address and stored in the
   core peer-group mapping system.  Note each mapping system layer could
   have a specific function or a specific circle of trust.

Farinacci & Cantrell      Expires July 14, 2018                 [Page 6]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

   This multi-layer mapping system can be illustrated:

              __________               ---------
             /   core   \  224.2.2.2  / layer-1 \
            | peer-group | --------> |     I     |
            |  224.1.1.1 |           |    / \    |
             \__________/            |   J---K   |
                  |                   \_________/
                  | 224.3.3.3
                  |
                  v
              ---------
             / layer-2 \
            |     X     |
            |    / \    |
            |   Y---Z   |
             \_________/

   Configured in xTRs A, B, and C (they make up the core peer-group):
     224.1.1.1 -> RLE: A, B, C

   core peer-group DMS, mapping state in A, B, and C:
     224.2.2.2 -> RLE: I, J, K
     224.3.3.3 -> RLE: X, Y, Z

   layer-1 peer-group DMS (inter-continental), mapping state in I, J, K:
      EID1 -> RLOCs: i(1), j(2)
      ...
      EIDn -> RLOCs: i(n), j(n)

   layer-2 peer-group DMS (intra-continental), mapping sate in X, Y, Z::
      EIDa -> RLOCs: x(1), y(2)
      ...
      EIDz -> RLOCs: x(n), y(n)

   The core peer-group multicast address 224.1.1.1 is configured in xTRs
   A, B and C so when each of them send Map-Register messages, they
   would all be able to maintain synchronized mapping state.  Any EID
   can be registered to this DMS but in this example, peer-group
   multicast group EIDs are being registered only to find other peer-
   groups.

   For example, lets say that xTR I boots up and it wants to find its
   other peers in its peer-group 224.2.2.2.  Group address 224.2.2.2 is
   configured so xTR I knows what group to join for its peer-group.  But
   xTR I needs a mapping system to register to, so the core peer-group
   is used and available to receive Map-Registers.  The other xTRs J and

Farinacci & Cantrell      Expires July 14, 2018                 [Page 7]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

   K in the peer-group do the same so when any of I, J or K needs to
   register EIDs, they can now send their Map-Register messages to group
   224.2.2.2.  Examples of EIDs being register are EID1 through EIDn
   shown above.

   When Map-Registers are sent to group 224.2.2.2, they are encapsulated
   by the LISP data-plane by looking up EID 224.2.2.2 in the core peer-
   group mapping system.  For the map-cache entry to be populated for
   224.2.2.2, the data-plane must send a Map-Request so the RLOCs I, J,
   and K are cached for replication.  To use the core peer-group mapping
   system, the data-plane must know of at least one of the RLOCs A, B,
   and/or C.

8.  Security Considerations

   Refer to the Security Considerations section of
   [I-D.ietf-lisp-rfc6833bis] for a complete list of security mechanisms
   as well as pointers to threat analysis drafts.

9.  IANA Considerations

   At this time there are no specific requests for IANA.

10.  References

10.1.  Normative References

   [RFC6830]  Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
              Locator/ID Separation Protocol (LISP)", RFC 6830,
              DOI 10.17487/RFC6830, January 2013,
              <https://www.rfc-editor.org/info/rfc6830>.

   [RFC6831]  Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "The
              Locator/ID Separation Protocol (LISP) for Multicast
              Environments", RFC 6831, DOI 10.17487/RFC6831, January
              2013, <https://www.rfc-editor.org/info/rfc6831>.

   [RFC6832]  Lewis, D., Meyer, D., Farinacci, D., and V. Fuller,
              "Interworking between Locator/ID Separation Protocol
              (LISP) and Non-LISP Sites", RFC 6832,
              DOI 10.17487/RFC6832, January 2013,
              <https://www.rfc-editor.org/info/rfc6832>.

   [RFC6833]  Fuller, V. and D. Farinacci, "Locator/ID Separation
              Protocol (LISP) Map-Server Interface", RFC 6833,
              DOI 10.17487/RFC6833, January 2013,
              <https://www.rfc-editor.org/info/rfc6833>.

Farinacci & Cantrell      Expires July 14, 2018                 [Page 8]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

   [RFC6836]  Fuller, V., Farinacci, D., Meyer, D., and D. Lewis,
              "Locator/ID Separation Protocol Alternative Logical
              Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836,
              January 2013, <https://www.rfc-editor.org/info/rfc6836>.

   [RFC8060]  Farinacci, D., Meyer, D., and J. Snijders, "LISP Canonical
              Address Format (LCAF)", RFC 8060, DOI 10.17487/RFC8060,
              February 2017, <https://www.rfc-editor.org/info/rfc8060>.

   [RFC8111]  Fuller, V., Lewis, D., Ermagan, V., Jain, A., and A.
              Smirnov, "Locator/ID Separation Protocol Delegated
              Database Tree (LISP-DDT)", RFC 8111, DOI 10.17487/RFC8111,
              May 2017, <https://www.rfc-editor.org/info/rfc8111>.

10.2.  Informative References

   [I-D.farinacci-lisp-ecdsa-auth]
              Farinacci, D. and E. Nordmark, "LISP Control-Plane ECDSA
              Authentication and Authorization", draft-farinacci-lisp-
              ecdsa-auth-01 (work in progress), October 2017.

   [I-D.ietf-lisp-rfc6833bis]
              Fuller, V., Farinacci, D., and A. Cabellos-Aparicio,
              "Locator/ID Separation Protocol (LISP) Control-Plane",
              draft-ietf-lisp-rfc6833bis-07 (work in progress), December
              2017.

   [I-D.ietf-lisp-sec]
              Maino, F., Ermagan, V., Cabellos-Aparicio, A., and D.
              Saucez, "LISP-Security (LISP-SEC)", draft-ietf-lisp-sec-14
              (work in progress), October 2017.

   [I-D.ietf-lisp-signal-free-multicast]
              Moreno, V. and D. Farinacci, "Signal-Free LISP Multicast",
              draft-ietf-lisp-signal-free-multicast-07 (work in
              progress), November 2017.

   [I-D.rodrigueznatal-lisp-pubsub]
              Rodriguez-Natal, A., Ermagan, V., Leong, J., Maino, F.,
              Cabellos-Aparicio, A., Barkai, S., Farinacci, D.,
              Boucadair, M., Jacquenet, C., and s.
              stefano.secci@lip6.fr, "Publish/Subscribe Functionality
              for LISP", draft-rodrigueznatal-lisp-pubsub-01 (work in
              progress), October 2017.

Farinacci & Cantrell      Expires July 14, 2018                 [Page 9]
Internet-Draft A Decent LISP Mapping System (LISP-Decent)   January 2018

Appendix A.  Acknowledgments

   The authors would like to thank the LISP WG for their review and
   acceptance of this draft.

   The authors would also like to give a special thanks to Roman
   Shaposhnik for several discussions that occured before the first
   draft was published.

Appendix B.  Document Change Log

   [RFC Editor: Please delete this section on publication as RFC.]

B.1.  Changes to draft-farinacci-lisp-decent

   o  Initial draft posted January 2018.

Authors' Addresses

   Dino Farinacci
   lispers.net
   San Jose, CA
   USA

   Email: farinacci@gmail.com

   Colin Cantrell
   Nexus
   Scottsdale, AZ
   USA

   Email: colin@nexus.io

Farinacci & Cantrell      Expires July 14, 2018                [Page 10]
muleroaa
Hero Member
*****
Offline Offline

Activity: 784
Merit: 520


GIF by SOCIFI


View Profile
March 20, 2018, 10:52:58 PM

Nexus is happy to Announce the Integration of the LISP

Network Architecture which allows

The Nexus Blockchain to run over a Secure Open Overlay

Read about it Here Now: https://nexusearth.com/news/nexus-integration-with-the-lisp-network-architecture/


This is pretty cool. I think Nexus is the first cryptocurrency to actually improve an existing internet protocol, the scope of this project just never ceases to amaze me.

                ▄▄▄▄▄▄▄▄▄▄                          ▄▄▄▄▄▄▄▄▄▄
             █████████████████                   █████████████████
         █████████████████████████           █████████████████████████
       █████████████████████████████       █████████████████████████████
     █████████████████████████████████   █████████████████████████████████
   ████████████▀           ▀██████████████████████████████████████████████
  ████████████▄▄███████████▄▄█████████▓▓▓███████████████████████████████████
 ▐██████████████▀         ▀██████████▓▓▓▓████████████████████████████████████
 ██████████████▄▄█████████▄▄█████████▓▓▓▓▓████████████████████████████████████
▐█████████████████▀      ▀██████████▓▓▓▓▓▓████████████████████████████████████▌
▐████████████████▄▄██████▄▄█████████▓▓▓▓▓▓▓███████████████████████████████████▌
▐██████████████████      ███████████▓▓▓▓▓▓▓███████████████████████████████████▌
▐██████████████████ ████ ████████████▓▓▓▓▓████████████████████████████████████
 ██████████████████ ████ ████████████▓▓▓▓▓███████████████    ████████████████
  █████████████████ ████ █████████████▓▓▓████████████████   █████████████   █
   ████████████████      ███████████████████████████████    ███████████
    ██████████████████████████████████ ██████████████████     ████████
      ███████████████████████████████     █████████████████
        ███████████████████████████         █████████████████▓
           ████████████████████                ███████████████████▓
               ▀▀▀▀▀▀▀▀▀▀▀▀▀                       ▀▀▀▀▀▀▀▀▀▀▀▀▀

▄▄▄████████▄▄▄
▄▄██████████████████▄▄
▄████████████████████████▄
▄████████████████████████████▄
████████████████████████████████
▓████████████████████████████████▓
███████████████████████▒░███████████
▄█████████████████▒░      ███████████▄
█████████████░░          ░████████████
█████████░              ░█████████████
██████████▓░░          ░██████████████
██████████████▓░       ███████████████
▀███████████████▒     ░██████████████▀
████████████████▒   ░███████████████
████████████████░ ░███████████████
████████████████████████████████
▀████████████████████████████▀
▀████████████████████████▀
▀▀██████████████████▀▀
 ▀▀▀████████▀▀▀
.
JOIN OUR
TELEGRAM
ShimmyShimmyCocoaBop
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
March 23, 2018, 06:22:21 PM

Quote
This is pretty cool. I think Nexus is the first cryptocurrency to actually improve an existing internet protocol, the scope of this project just never ceases to amaze me.

Great! Fantastic! Farout!
Now if we can just keep it in the top 100 of all coins, let alone the top 20.
kubricktrader
Full Member
***
Offline Offline

Activity: 371
Merit: 103


View Profile
March 24, 2018, 03:26:01 AM

Nexus seems massively undervalued at the moment. As market recovers I expect big moves from this one.
spaid
Newbie
*
Offline Offline

Activity: 12
Merit: 27


View Profile
March 24, 2018, 12:27:45 PM

Free Giveaway For 100 NXS (at least) - Week 3

Congrats to @from200to3millions for winning 100 NXS this week. https://microcapcrypto.com/week-3-winner/

Next week I am going to have multiple winners next week, so check back for the new announcement tomorrow.

The link below has the entry form. If you do not have a Slack or Discord User Name to enter, please just make a note in the Name field that you are using a Bitcointalk name instead and I will get in touch with you if you win.

Nexus Giveaway Entry Page

The winner of the free giveaway will be announced on the Crypto & Chat Show Friday night March 30th at 8:00 PM EST. You do not have to listen to win, but if you want to listen go to.

Crypto & Chat Show

The winner of the week 2 giveaway was @thymusnxs from Slack. So far we've given away over 310 NXS in March. Looking forward to giving away more NXS this week!
yumcoins
Newbie
*
Offline Offline

Activity: 31
Merit: 0


View Profile
March 24, 2018, 06:15:24 PM

<expletive> Anastasiya, banned ...

Just FYI, I have nothing to do with the coin or the team, but I did report your comment on the basis that ugly, sexist personal attacks don't belong here.  Air your grievances all you want, for all I care, but please do so in a civil way.

This also isn't the thread for promoting your conspiracy person - this is a thread for discussing Nexus.  That's not a judgement about whether you're right or wrong, it's trying to keep this thread useful for people who're looking for information or discussion about the coin and project.
limitup
Newbie
*
Offline Offline

Activity: 33
Merit: 0


View Profile
March 24, 2018, 06:50:34 PM

Nexus seems massively undervalued at the moment. As market recovers I expect big moves from this one.

..and shitcoins are ranked higher in lamboland
crypto_curious
Full Member
***
Offline Offline

Activity: 490
Merit: 104


★777Coin.com★ Fun BTC Casino!


View Profile
March 28, 2018, 10:16:04 AM

Hello guys,

I recently find out about Nexus and I like the idea. I invested into it, I will be hodling:)

Quick question regarding staking:
I sent coins to fully synchronized wallet, encrypted it, unlocked for minting.
Now I have coins confirmed (21 confirmations), wallet unlock for minting, and I have question mark still:
"Staking Inactive... No coins to Stake"

When it will become active? How long does it take? Do I need to anything else? Thanks!

kchulani
Full Member
***
Offline Offline

Activity: 308
Merit: 100



View Profile
March 28, 2018, 11:54:27 AM

I would like to know if anyone knows if any of the cube satellites will be launching this year or next year for testing? Ireally love this project and I have been hodling on since the ICO, can't wait to see whats next.

plurkstar
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
March 28, 2018, 04:19:17 PM

I would like to know if anyone knows if any of the cube satellites will be launching this year or next year for testing? Ireally love this project and I have been hodling on since the ICO, can't wait to see whats next.

Nexus Coin do not have an ICO.. Are you with the right coin ? The cube satellites will be launching either end of this year or early next year. There is no fixed date for the launch.
stan86
Hero Member
*****
Offline Offline

Activity: 1050
Merit: 511



View Profile
March 28, 2018, 06:41:48 PM

The Nexus Wallet Update 0.2.4.0 is Here

Read all About the Features and Download Here Now: https://nexusearth.com/wallet/

                 ██            ██
               ██████        ██████
            ████████████      ██████
        ███████████████████    ██████
     ███████████    ██████████  ██████
  ██████████    ███    ████████  ▀█████
  ██████    ███████████   ██████  █████
  █████   ██████  ██████   █████  █████
  █████    ███      ███    █████  █████
  █████  ██            ██  █████  █████
  █████  ███          ███  █████  █████
  █████  ███████   ██████  █████  █████
  █████  ████████████████  █████  █████
  █████  ████████████████  █████  █████
  █████  ████  █████ ████  ████  ██████
  █████  ████   ███  ████  ███  ██████
  █████  ████    █   ████  █   ██████ 
  █████  ████        ██      ███████     
    ███  ████        █     ███████         
      █  ████         ▄██  █████       
           ██        ████  ███
            █        ██▀
`AiBB`  覧覧覧覧覧
HARNESSING THE POWER OF Ai IN CRYPTO
▐ -
`BUY TOKENS`
-▐   Twitter
  Telegram
  Facebook
|WP
Reddit
Medium
crypto_curious
Full Member
***
Offline Offline

Activity: 490
Merit: 104


★777Coin.com★ Fun BTC Casino!


View Profile
March 29, 2018, 12:08:18 PM

Hello,

I am trying to mine solo with Nvidia cards. Unfortunately, miner on Nexus website (SKMiner-v.0.1.3_optimized_by_Mumus) doesn't work. Hashrate is showing zero for 15 seconds and then miner closes automatically. Other miner for pooled mining (different version of SKMiner) work just fine on pool.

How to mine solo on Nvidia? Is there any new version of SKMiner for solo?

Pages: « 1 ... 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 [363] 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!