btc资讯
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # 链上指标RUPL是什么?如何应用RUPL指标抄底和逃顶?RUPL历史周期顶部分析 <div style="background:#fff8e1;border-left:4px solid #F0B90B;padding:12px 16px;margin:0 0 24px;border-radius:0 6px 6px 0;color:#555;font-size:14px;line-height:1.7;">📋 链上指标RUPL是相对未实现损益,它衡量了加密货币市场整体的盈亏状态,通过比较当前价格与每个币最后交易价格,计算出市场中处于盈利和亏损状态的代币总价值,并按市值标准化,是判断市场顶底的重要晴雨表,那么,如何应用RUPL指标抄底和逃顶?下文将为大家详细介绍RUPL</div><div id="content"> <p>RUPL是相对未实现损益,可以拆分成RUP和RUL,分别代表相对未实现盈利、相对未实现亏损,这个数据最主要的用途是表示当前整体市场的盈亏状况。这个数据最主要的用途,是表示当前整体市场的盈亏状况。</p> <p>那么究竟链上指标RUPL是什么?如何应用RUPL指标抄底和逃顶?接下来,将为大家详细分析市场晴雨表 RUPL(II)- 最强顶部讯号 &amp; 历史周期顶部,关于 RUPL 指标的详细说明,可参考本文。</p> <p style="text-align:center"><img alt="链上指标RUPL是什么?如何应用RUPL指标抄底和逃顶?RUPL历史周期顶部分析" height="375" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/510/f_29464510_1.jpg" width="750"/></p> <h2>链上指标RUPL是什么?</h2> <p>RUPL指标(Relative Unrealized Profit &amp; Loss),中文是<strong>相对未实现损益</strong>,是衡量加密货币市场整体盈亏状况的重要链上指标,它由相对未实现盈利 (RUP) 和相对未实现亏损 (RUL) 组成,通过比较当前价格与过去转移价格来评估市场中持币者的盈利/亏损程度。该指标常被用于识别市场底部和顶部,例如高RUPL值可能预示市场过热,接近顶部。</p> <p>换句话说,Unrealized Profit 就是目前市场上「未实现利润的总和」;而RUP 则是根据市值,将此数据进行标准化,以便比对不同时期的市场盈利状况。</p> <p>RUL 的算法与RUP 的逻辑完全相同,在此就不多做赘述。</p> <p style="text-align:center"><img alt="链上指标RUPL是什么?" height="602" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/511/f_29464511_1.jpg" width="1078"/></p> <p>如上图,绿色线是RUP,红色线是RUL。</p> <p>我们可以发现:价格与RUP 是高度正相关、与RUL 是高度负相关。</p> <p>这点很直观,因为随着币价上涨,未实现盈利筹码的利润总和自然会随之增加。</p> <p>但若我们对上图做进一步观察,会发现RUL 在少数时段中会超过RUP(红线在绿线之上),这意味着市场整体的未实现损益状况是负值,这种状况是否具有特别的意义呢?请接着往下阅读。</p> <h3>RUPL指标的构成</h3> <ul><li><strong>RUP (Relative Unrealized Profit)</strong>: 相对未实现盈利,显示当前有利可图的持币者的未实现盈利总和。</li><li><strong>RUL (Relative Unrealized Loss)</strong>: 相对未实现亏损,显示当前处于亏损状态的持币者未实现亏损总和。</li></ul> <h3>RUPL的计算原理</h3> <ul><li><strong>识别盈利/亏损筹码</strong>: 将当前市场价格与每枚代币最后一次转移时的价格进行比较。</li><li><strong>计算未实现损益</strong>:<ul><li><strong>未实现盈利</strong>: 现有价格 &gt; 最后转移价格的筹码,其盈利额乘以数量,得出总未实现利润。</li><li><strong>未实现亏损</strong>: 现有价格 &lt; 最后转移价格的筹码,其亏损额乘以数量,得出总未实现亏损。</li></ul></li><li><strong>标准化</strong>: 将上述未实现损益数据对当时市值进行标准化处理。</li></ul> <h3>主要用途</h3> <ul><li><strong>判断市场情绪</strong>: 整体RUPL数值反映了市场持币者的普遍盈利或亏损状态。</li><li><strong>识别市场周期</strong>: 在牛市中,高RUP值可能预示着顶部,而在熊市中,高RUL值可能预示着底部。</li></ul> <h2>RUPL 的抄底应用</h2> <p>古语有云:「别人恐惧时我贪婪」,当市场的筹码持有者,整体平均处于亏损状态时,或许就是一个值得我们进场收筹码的时候。</p> <p style="text-align:center"><img alt="RUPL 的抄底应用" height="606" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/512/f_29464512_1.jpg" width="1082"/></p> <p>如上图,我将RUL &gt; RUP 的时间段标记出来,得到这张讯号图。</p><div style="background:#fff9f0;border-left:4px solid #F0B90B;padding:16px 18px;margin:24px 0;font-size:14px;line-height:1.8;"> <p style="margin:0 0 8px;font-size:15px;font-weight:bold;color:#333;">📊 在币安交易 BTC — 全球最深流动性</p> <p style="margin:0 0 10px;color:#555;">币安拥有全球最大现货+合约市场,BTC/USDT 交易对深度极佳,滑点低、费率全网最优,通过专属链接注册享 <strong>20% 手续费折扣</strong>。</p> <ul style="margin:0 0 10px;padding-left:20px;color:#444;"> <li>🖥️ 进入专业交易界面:<a href="https://www.binance.com/trade/BTC_USDT?layout=pro&amp;ref=B2345&amp;type=spot" rel="sponsored" target="_blank">币安 BTC/USDT 现货</a></li> <li>📈 合约交易入口:<a href="https://www.binance.com/join?ref=B2345" rel="sponsored" target="_blank">开通合约账户</a></li> <li>📚 完整交易教程:<a href="https://www.bitaigen.com/binance" rel="sponsored" target="_blank">币安使用指南2026</a></li> </ul> <p style="margin:0;font-size:12px;color:#888;">✅ 邀请码 <strong>B2345</strong> · 注册即享手续费20%减免</p> </div> <p>我们可以很清楚的发现:当RUL &gt; RUP 时,基本都对应到周期性的大底部!</p> <p>这绝非单纯的刻舟求剑,其逻辑在于:</p> <p>「当市场整体平均处于亏损状态时,意味着套牢者很可能因为价格过低,而不愿抛售手中的筹码」,在抛压大幅降低的情况下,后续只要有稍微增强的买盘,就可能让趋势反转,开始上涨。</p> <p>这个逻辑与先前文章中介绍的LTH-RP 抄底策略非常类似,有兴趣的读者可以翻阅先前的贴文。</p> <h2>RUPL 抄底模型的设计逻辑分享</h2> <p>接着,让我们暂时忽略RUL,专注于RUP 图表本身,我们会发现RUP 在历史上的底部数值其实非常接近。</p> <p style="text-align:center"><img alt="RUPL 抄底模型的设计逻辑分享" height="616" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/513/f_29464513_1.jpg" width="1074"/></p> <p>举例而言,我在RUP 图表上新增一条0,4 的水平线,让我们可以清楚的看到RUP &lt; 0.4 的位置。(此处的0.4 是一个可调参数,后续会再提一次)</p> <p>在发现RUP 具有一个相对明显的底部区域时,我们便可把RUP &lt; 0.4 的条件叠加到先前「RUP &lt; RUL」的条件上,进行讯号上的二次过滤,得到的结果如下:</p> <p style="text-align:center"><img alt="RUPL 抄底模型的设计逻辑分享_图2" height="600" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/514/f_29464514_1.jpg" width="1080"/></p> <p>这是一个在设计模型时很常用的方法,目的是透过讯号筛网达到过滤的效果,让我们最终设计出的模型能够更加精确。</p> <p>上图的两个条件(RUP &lt; 0.4 &amp; RUP &lt; RUL),过滤效果其实并没有到非常明显,但仔细看还是可以发现,确实有比单纯的RUP &lt; RUL 更严格。</p> <p>在此,如果将0.4 调小(例如调整成0.38),就能让整体讯号更加严格;但在调整参数的过程中,仍须注意Overfitting 的问题,毕竟单纯根据历史数据去对模型进行拟合,很可能在未来就会失效!</p> <h2>RUPL 的逃顶应用</h2> <p>正如前篇文章结语所说,今天的文章,我将分享一个 RUPL 在逃顶上的强大用法。在这个用法中,我们只需要用到 RUP,暂时不需要理会 RUL:</p> <p><strong>当 RUP 与 $BTC 价格走势出现背离时,很可能意味着顶部出现</strong></p> <p>1、精确来说,当 $BTC 价格创出更高的高点,但 RUP 却创出较低的高点时,背离即成立。</p> <p>2、其逻辑在于:  </p> <p>前篇文章提到,RUP 的计算需要先加总市场上的 Unrealized Profit。大量筹 码持有者的 Unrealized Profit 远高于小量筹 码持有者,按理来说,当价格创出更高的高点时,RUP 也应该跟着上升。但如果出现上述的背离(价格更高,市场的盈利状态反而较低),那么唯一的可能就是「持有大量筹 码的持有者已经开始出售筹 码,进行派发」。</p> <p>3、此逻辑与 Realized Profit 类似,可以作为交叉验证的参考。</p> <p>以上就是「为何 RUP 背离可以作为顶部信号」的逻辑说明,不过使用时仍需注意:对于市场阶段的判断,最正确的做法应结合其他链上指标一起观察,才能最大程度避免「以管窥天」的误区。</p><div style="background:#e8f5e9;border:2px solid #66bb6a;border-radius:8px;padding:16px 18px;margin:24px 0;font-size:14px;line-height:1.8;"> <p style="margin:0 0 8px;font-size:15px;font-weight:bold;color:#333;">🌐 币安 Web3 钱包 · 一站式管理链上资产</p> <p style="margin:0 0 10px;color:#555;">内置 DEX 聚合器、跨链桥、DeFi 收益,支持50+主流公链,私钥自托管安全透明。</p> <ul style="margin:0 0 10px;padding-left:20px;color:#444;"> <li>🔗 Web3 钱包邀请链接:<a href="https://web3.binance.com/referral?ref=MW7E7Y08" rel="sponsored" target="_blank">立即体验(邀请码 MW7E7Y08)</a></li> <li>💱 现货账户同步开通享手续费减免:<a href="https://accounts.binance.com/register?ref=B2345" rel="sponsored" target="_blank">注册币安现货(邀请码 B2345)</a></li> <li>📖 完整 DeFi 教程:<a href="https://www.bitaigen.com/binance" rel="sponsored" target="_blank">币安12大专题教程</a></li> </ul> <p style="margin:0;font-size:12px;color:#888;">✅ Web3 + 现货双账户联动,链上链下资产统一管理</p> </div> <h2>历史周期顶部详细分析</h2> <p>了解了 RUP 背离的逻辑后,如果不实际验证,那都只是纸上谈兵。所以在这一部分,我将带大家回顾 $BTC 的历次历史性顶部:</p> <h3>2013 年牛市顶部</h3> <p style="text-align:center"><img alt="2013 年牛市顶部" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/515/f_29464515_1.jpg"/></p> <p>如上图,绿色线是 RUP,黑色线是 BTC 价格。在顶部发生时,价格与 RUP 出现了「三段式背离」,<strong>随着价格连续创出两次更高高点,对应的 RUP 却连续创出较低高点</strong>,完全符合前面描述的 RUP 背离顶部信号</p> <h3>2017 年牛市顶部</h3> <p style="text-align:center"><img alt="2017 年牛市顶部" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/516/f_29464516_1.jpg"/></p> <p>如图,在 2017 年的顶部中,同样出现了 RUP 的背离信号。在这次顶部中,RUP 在价格达到最高点时,出现了一次 RUP 背离;随后在价格挣扎反弹时,又出现了第二次背离,算是给足了逃命机会</p> <h3>2021 年牛市顶部</h3> <p style="text-align:center"><img alt="2021 年牛市顶部" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/517/f_29464517_1.jpg"/></p> <p>如图,2021 年出现了比较特殊的「双顶结构」。我分别针对两次顶部进行分析。第一顶,情况与 2013 年类似,出现了「三段式背离」;第二顶,同样在顶部期出现了一次 RUP 背离。</p> <p>以上,目前出现过的三次历史性周期顶部,无一例外都出现了 RUP 背离,当然,这并不代表未来每次顶部一定会出现背离,但就目前数据来看,每次都未曾例外。那... 这一轮呢?</p> <h2>2025年潜在顶部:当前市场阶段分析  </h2> <p>这里直接上图:</p> <p style="text-align:center"><img alt="2025年潜在顶部:当前市场阶段分析" loading="lazy" src="https://g.udn.com.tw/upfiles/B_G_/G_114761846439584705/PSN_PHOTO/518/f_29464518_1.jpg"/></p> <p>可以看到,<strong>在这一轮周期中,目前已经出现过「一次」RUP 背离的顶部信号了</strong>。结合逃顶周报的内容,或是从 URPD、Cointime Price、Realized Profit 等数据中,其实都能或多或少发现一些顶部出现的迹象。</p> <p>稍微值得乐观的是:根据前三轮顶部,<strong>除了 2021 年第二顶以外,2013、2017、2021 年第一顶,都至少出现过两次背离</strong>,而目前只出现了一次。</p> <p><strong>因此,根据历史规律,如果短期内 $BTC 价格再创一次新高,极大概率会出现类似 2013、2021 年第一顶的三段式背离。届时无疑是值得所有读者们重点关注的逃顶机会</strong></p> <h2>总结</h2> <p>本文主要向大家分享了使用RUP 数据作为逃顶依据的逻辑,同时也透过分析历史的周期性顶部,对这个用法进行验证。最后,敝人也针对目前的市场状况明牌提示顶部的警讯,如果后续各项链上数据有出现异动,敝人必会第一时间发文告知各位。还请各位读者保持关注,我们一起打出一场漂亮的撤退。</p> <p>以上就是链上指标RUPL是什么?如何应用RUPL指标抄底和逃顶?RUPL历史周期顶部分析的详细内容,更多关于RUPL指标新手指南的资料请关注Bitaigen(比特根)其它相关文章!</p><div style="background:#fffde7;border:2px solid #F0B90B;border-radius:8px;padding:16px 18px;margin:24px 0;font-size:14px;line-height:1.8;"> <p style="margin:0 0 8px;font-size:15px;font-weight:bold;color:#333;">🏆 币安 Binance · 全球最大加密货币交易所</p> <p style="margin:0 0 10px;color:#555;">全球交易量第一,500+交易对,中国大陆可直接访问,通过专属链接注册享 <strong>20% 手续费永久减免</strong>。</p> <ul style="margin:0 0 10px;padding-left:20px;color:#444;"> <li>📖 完整使用指南(2026最新):<a href="https://www.bitaigen.com/binance" rel="sponsored" target="_blank">12大专题教程</a></li> <li>🇨🇳 中国区专属注册通道:<a href="https://basebiance.com/binancecn" rel="sponsored" target="_blank">立即注册</a></li> <li>📱 安卓APK直接下载:<a href="https://basebiance.com/binanceapkcn" rel="sponsored" target="_blank">点击下载</a></li> <li>🌐 官网注册(邀请码 <strong>B2345</strong>):<a href="https://accounts.binance.com/register?ref=B2345" rel="sponsored" target="_blank">accounts.binance.com</a></li> </ul> <p style="margin:0;font-size:12px;color:#888;">✅ 手续费减免20% · 新用户福利 · 安全合规运营</p> </div> </div>

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully