[{"data":1,"prerenderedAt":70},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fcore-tech\u002Fnode-standard-operation-mode":3,"docs-surround-\u002Fdocs\u002Fcore-tech\u002Fnode-standard-operation-mode":59},{"id":4,"title":5,"body":6,"description":50,"extension":51,"image":52,"meta":53,"navTitle":52,"navigation":54,"path":55,"seo":56,"stem":57,"__hash__":58},"docs\u002Fdocs\u002Fcore-tech\u002FNode-standard-operation-mode.md","Node Standard Operation Mode",{"type":7,"value":8,"toc":45},"minimark",[9,18,28,31,34,39,42],[10,11,12,13,17],"p",{},"According to the protocol Node advertises its tip (header) to all the connected peers, which may ",[14,15,16],"em",{},"potentially"," be interested in it. Potentially interested means the following:",[19,20,21,25],"ul",{},[22,23,24],"li",{},"The peer tip has lower Chainwork",[22,26,27],{},"The peer tip has the same Chainwork, but the tip is different\nImmediately after connecting the tip is always sent, because the peer tip is not known yet (by default assumed empty). Then, after each state transition, the tip is sent only if either of the above criterias is satisfied.",[10,29,30],{},"In addition to the advertising, Nodes synchronize actively: request and send headers and blocks. The data request logic is designed such that all the nodes aim to reach the tip of the heaviest branch, but in practice nodes would also request any data to achieve a higher state than the current (so that they're not easily paralyzed by revealing a non-existing tip).",[10,32,33],{},"There are 2 types of requests: headers and block.",[35,36,38],"h2",{"id":37},"headers","Headers",[10,40,41],{},"sends its tip (header) to every peer (be it client or other Node) when it connects.",[10,43,44],{},"Then, if the peer tip is also received, the Node",{"title":46,"searchDepth":47,"depth":47,"links":48},"",2,[49],{"id":37,"depth":47,"text":38},"According to the protocol Node advertises its tip (header) to all the connected peers, which may potentially be interested in it. Potentially interested means the following:","md",null,{},true,"\u002Fdocs\u002Fcore-tech\u002Fnode-standard-operation-mode",{"description":50},"docs\u002Fcore-tech\u002FNode-standard-operation-mode","KpFp-xEMig6tpObhqvEAvUuVBR4JGBwHLUmpNTynU3Q",[60,65],{"title":61,"path":62,"stem":63,"description":64,"children":-1},"-- DEPRECATED --","\u002Fdocs\u002Fcore-tech\u002Fnode-initial-synchronization-(deprecated)","docs\u002Fcore-tech\u002FNode-initial-synchronization-(DEPRECATED)","BEAM Node initially operates in Sync mode, then eventually it switches to the Standard mode.",{"title":66,"path":67,"stem":68,"description":69,"children":-1},"One Side Payments","\u002Fdocs\u002Fcore-tech\u002Fone-side-payments","docs\u002Fcore-tech\u002FOne-side-payments","In MW in order to create a valid transaction all the parties must collaborate. Here we'll present a one-side payment scheme, which, after initial setup, allows arbitrary senders to pay specified (fixed) values to a particular receiver, without any further collaboration from the receiver side.",1783006076760]